Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c4c977dbebb64f876ffafe15c8652d33389692e1a9240d00f518f4f62f2d1de

Tx prefix hash: 1b579d3211b3ce1bb0eaee47b9425205df972fb249050b8d43edd2affa2b789f
Tx public key: 96ed171ff5c358abc224ebb74ee01f2cec7f050a23d4ee2d3be0e8e70943a7aa
Timestamp: 1709060097 Timestamp [UCT]: 2024-02-27 18:54:57 Age [y:d:h:m:s]: 00:206:12:39:45
Block: 966864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147927 RingCT/type: yes/0
Extra: 0196ed171ff5c358abc224ebb74ee01f2cec7f050a23d4ee2d3be0e8e70943a7aa0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d166ae208fd322649061ede0f13a5fd2400cb82a2c8b316afa7e86727c9609d1 0.600000000000 1426635 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": 966874, "vin": [ { "gen": { "height": 966864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d166ae208fd322649061ede0f13a5fd2400cb82a2c8b316afa7e86727c9609d1" } } ], "extra": [ 1, 150, 237, 23, 31, 245, 195, 88, 171, 194, 36, 235, 183, 78, 224, 31, 44, 236, 127, 5, 10, 35, 212, 238, 45, 59, 224, 232, 231, 9, 67, 167, 170, 2, 17, 0, 0, 0, 1, 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