Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 202d6c16a584e423e71fce0c8dcce6e9b5e72f743d3fb49de26cc3a6e9109e31

Tx prefix hash: 2d44afba40d5d6904b7189e6f97738268ef46efae90a426f28eaa56efba0c60f
Tx public key: d99715fe3501ee035bfba256bb9e0cf6ef44266c4eef46f0258629e72f79bdcf
Timestamp: 1684573407 Timestamp [UCT]: 2023-05-20 09:03:27 Age [y:d:h:m:s]: 01:320:18:08:58
Block: 764106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490451 RingCT/type: yes/0
Extra: 01d99715fe3501ee035bfba256bb9e0cf6ef44266c4eef46f0258629e72f79bdcf02110000000c33af99f4000000000000000000

1 output(s) for total of 1.803847459000 dcy

stealth address amount amount idx
00: ed649df29f571e4cf6d1ed0c5c08a6ec6b3883d7dfc8d5fc347bc90656c3beb4 1.803847459000 1212999 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": 764116, "vin": [ { "gen": { "height": 764106 } } ], "vout": [ { "amount": 1803847459, "target": { "key": "ed649df29f571e4cf6d1ed0c5c08a6ec6b3883d7dfc8d5fc347bc90656c3beb4" } } ], "extra": [ 1, 217, 151, 21, 254, 53, 1, 238, 3, 91, 251, 162, 86, 187, 158, 12, 246, 239, 68, 38, 108, 78, 239, 70, 240, 37, 134, 41, 231, 47, 121, 189, 207, 2, 17, 0, 0, 0, 12, 51, 175, 153, 244, 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