Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54a5a868de97cb479464d1551b6cea9904213b3a1e19e965eecda82c7cee65e2

Tx prefix hash: 727b79aa19de6a748e77d25d7af9f5f0777b968757db2d1a3d81f381c8e5692e
Tx public key: 6eb7c2dc4909fa940e34f081da29e993215f4c368ed928a32f218d0bebe162c7
Timestamp: 1574490750 Timestamp [UCT]: 2019-11-23 06:32:30 Age [y:d:h:m:s]: 05:111:18:39:43
Block: 15137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1222930 RingCT/type: yes/0
Extra: 016eb7c2dc4909fa940e34f081da29e993215f4c368ed928a32f218d0bebe162c70211000000060b4dd45a000000000000000000

1 output(s) for total of 546.821673011000 dcy

stealth address amount amount idx
00: 2ce2beae2a8e4f245607d11ba7edf720151b7f407a9699a259082f31a9a031d2 546.821673011000 20027 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": 15147, "vin": [ { "gen": { "height": 15137 } } ], "vout": [ { "amount": 546821673011, "target": { "key": "2ce2beae2a8e4f245607d11ba7edf720151b7f407a9699a259082f31a9a031d2" } } ], "extra": [ 1, 110, 183, 194, 220, 73, 9, 250, 148, 14, 52, 240, 129, 218, 41, 233, 147, 33, 95, 76, 54, 142, 217, 40, 163, 47, 33, 141, 11, 235, 225, 98, 199, 2, 17, 0, 0, 0, 6, 11, 77, 212, 90, 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