Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0e50d0b2758d7a9f7dbc64055c976126660c9abedd05dbaed6046016b36cc366

Tx prefix hash: 215f055913f36d5290f29a1ff56e256ff299c2098a52ff0d1aa6c3176b0a1d01
Tx public key: cf51e8857af5877566580343f8f68fc6513f69a3bfc56861d969d396d21b6bda
Timestamp: 1696459638 Timestamp [UCT]: 2023-10-04 22:47:18 Age [y:d:h:m:s]: 01:166:23:29:34
Block: 862589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380409 RingCT/type: yes/0
Extra: 01cf51e8857af5877566580343f8f68fc6513f69a3bfc56861d969d396d21b6bda021100000005faf35c9c000000000000000000

1 output(s) for total of 0.850911912000 dcy

stealth address amount amount idx
00: b010d4311c8497a80e9f857eeecd20d6c8a77d8e8ad876f09cdf057d395b9bbb 0.850911912000 1317017 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 862599, "vin": [ { "gen": { "height": 862589 } } ], "vout": [ { "amount": 850911912, "target": { "key": "b010d4311c8497a80e9f857eeecd20d6c8a77d8e8ad876f09cdf057d395b9bbb" } } ], "extra": [ 1, 207, 81, 232, 133, 122, 245, 135, 117, 102, 88, 3, 67, 248, 246, 143, 198, 81, 63, 105, 163, 191, 197, 104, 97, 217, 105, 211, 150, 210, 27, 107, 218, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8