Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50e1a691a8230d0a51c0eebb25aa9a953b7b1730cd38939af97789063aa08dc1

Tx prefix hash: 492bf753f41c559cf55e4a1045fa31137fbb5f8bf0f80896640492920061ecf0
Tx public key: 9f13560d9e3ca3c25031de70dc1e8edd30c298155ee1b59ee070ff1dddef2d80
Timestamp: 1705442309 Timestamp [UCT]: 2024-01-16 21:58:29 Age [y:d:h:m:s]: 01:078:03:12:54
Block: 936849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316936 RingCT/type: yes/0
Extra: 019f13560d9e3ca3c25031de70dc1e8edd30c298155ee1b59ee070ff1dddef2d8002110000004a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 432ae26c51f338cb6e76b5566e6d0c5d82db434368c49fe3d5f1df47d7745e69 0.600000000000 1394891 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": 936859, "vin": [ { "gen": { "height": 936849 } } ], "vout": [ { "amount": 600000000, "target": { "key": "432ae26c51f338cb6e76b5566e6d0c5d82db434368c49fe3d5f1df47d7745e69" } } ], "extra": [ 1, 159, 19, 86, 13, 158, 60, 163, 194, 80, 49, 222, 112, 220, 30, 142, 221, 48, 194, 152, 21, 94, 225, 181, 158, 224, 112, 255, 29, 221, 239, 45, 128, 2, 17, 0, 0, 0, 74, 122, 156, 244, 199, 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