Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e914fde21388a0d24cd036fa3047f7c5a3593185564e438b6a21fcfcd432c90

Tx prefix hash: a0bfc9cfa4b13a7b4c1b214ad18d2745390bdb9a1e04784e9d84c5de3f952b8e
Tx public key: 10682dc9b1c60da7b4a1c0582dba15dcc1e13fd2d73346274652198672d43aa6
Timestamp: 1636956846 Timestamp [UCT]: 2021-11-15 06:14:06 Age [y:d:h:m:s]: 03:038:18:00:43
Block: 374640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 806463 RingCT/type: yes/0
Extra: 0110682dc9b1c60da7b4a1c0582dba15dcc1e13fd2d73346274652198672d43aa6021100000035d6e4826b000000000000000000

1 output(s) for total of 35.209718022000 dcy

stealth address amount amount idx
00: 7b409992da6c81aea8ddc3b1ad7fd06887311be9ffbc174c57e14b72fcdbd6c5 35.209718022000 758250 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": 374650, "vin": [ { "gen": { "height": 374640 } } ], "vout": [ { "amount": 35209718022, "target": { "key": "7b409992da6c81aea8ddc3b1ad7fd06887311be9ffbc174c57e14b72fcdbd6c5" } } ], "extra": [ 1, 16, 104, 45, 201, 177, 198, 13, 167, 180, 161, 192, 88, 45, 186, 21, 220, 193, 225, 63, 210, 215, 51, 70, 39, 70, 82, 25, 134, 114, 212, 58, 166, 2, 17, 0, 0, 0, 53, 214, 228, 130, 107, 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