Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 649d43a2df9c08c803ed1a5987a474ef0fdf8fcda8d358b44553f1d979bd5a16

Tx prefix hash: 2caf942b2fae6d7f0126feeab414ed333a9ed9a66b40666a8fd955244ddf0c79
Tx public key: bc017ffcb5de455bf11e086143578254bd49884c293dd7f242d8dcf646ad7788
Timestamp: 1764313773 Timestamp [UCT]: 2025-11-28 07:09:33 Age [y:d:h:m:s]: 00:025:03:29:34
Block: 1421810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17987 RingCT/type: yes/0
Extra: 01bc017ffcb5de455bf11e086143578254bd49884c293dd7f242d8dcf646ad77880211000000074e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35e144b4d7d4ffbe04de5a1ea34cba1718f1f0d40c170751524f6cee8831412d 0.600000000000 1910371 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": 1421820, "vin": [ { "gen": { "height": 1421810 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35e144b4d7d4ffbe04de5a1ea34cba1718f1f0d40c170751524f6cee8831412d" } } ], "extra": [ 1, 188, 1, 127, 252, 181, 222, 69, 91, 241, 30, 8, 97, 67, 87, 130, 84, 189, 73, 136, 76, 41, 61, 215, 242, 66, 216, 220, 246, 70, 173, 119, 136, 2, 17, 0, 0, 0, 7, 78, 123, 252, 9, 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