Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 100d10644e4b1893f0b811e8baaa6f2e95d83c0aeaf08e1585551dae465209a0

Tx prefix hash: 9c435d118617c3a5d9b3d0da804fb3eb546d8be795745ff891937ed0811fda65
Tx public key: b0557ee81cb273171126dd74c2c783b232a1bd2000732893b8e3dcb9fbc025d9
Timestamp: 1703079656 Timestamp [UCT]: 2023-12-20 13:40:56 Age [y:d:h:m:s]: 01:141:07:43:52
Block: 917281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362143 RingCT/type: yes/0
Extra: 01b0557ee81cb273171126dd74c2c783b232a1bd2000732893b8e3dcb9fbc025d902110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cb979b5c765947eb727dbd3cf4298c47026feb870f1b89628f555d7c3e8d689 0.600000000000 1374851 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": 917291, "vin": [ { "gen": { "height": 917281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cb979b5c765947eb727dbd3cf4298c47026feb870f1b89628f555d7c3e8d689" } } ], "extra": [ 1, 176, 85, 126, 232, 28, 178, 115, 23, 17, 38, 221, 116, 194, 199, 131, 178, 50, 161, 189, 32, 0, 115, 40, 147, 184, 227, 220, 185, 251, 192, 37, 217, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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