Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0de71f75324df15febaf1c7fc683bf52884f4214f59d7f5b2b387f01f609e47a

Tx prefix hash: ea6d6a70a929bf4f7f11b674549630cbaa2f93395b287edb7aa2d8c926c91277
Tx public key: fe1d81bd107f34b0138daa9b38e94264c707207b33ce0bea20195c1d2c0858e0
Timestamp: 1732580481 Timestamp [UCT]: 2024-11-26 00:21:21 Age [y:d:h:m:s]: 00:167:05:20:51
Block: 1161753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119349 RingCT/type: yes/0
Extra: 01fe1d81bd107f34b0138daa9b38e94264c707207b33ce0bea20195c1d2c0858e00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04b41c8cb2d1cf161fb1470e41bbda6e1154d8145f8067f166becdf0da559b1f 0.600000000000 1647408 of 15

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": 1161763, "vin": [ { "gen": { "height": 1161753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04b41c8cb2d1cf161fb1470e41bbda6e1154d8145f8067f166becdf0da559b1f" } } ], "extra": [ 1, 254, 29, 129, 189, 16, 127, 52, 176, 19, 141, 170, 155, 56, 233, 66, 100, 199, 7, 32, 123, 51, 206, 11, 234, 32, 25, 92, 29, 44, 8, 88, 224, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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