Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd203af8be421fd3c99ddc7fd67fd37fddf5f170c4167ce5c58bb5466bfacc97

Tx prefix hash: 914384ee7aff30e11ffcdc3480cb8e3bef50aa7dfaf8ea7b4e6f6a47866843fa
Tx public key: d1b1b1dc5ec7f63e9010629901bc69e121d495254a7aae02f2472d2661490115
Timestamp: 1709441902 Timestamp [UCT]: 2024-03-03 04:58:22 Age [y:d:h:m:s]: 01:036:23:29:59
Block: 970028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287427 RingCT/type: yes/0
Extra: 01d1b1b1dc5ec7f63e9010629901bc69e121d495254a7aae02f2472d266149011502110000000249a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e90e13e03d2121354301953488cddd92b4868bbc10fb3e12c4d15b9cbf01f857 0.600000000000 1429877 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": 970038, "vin": [ { "gen": { "height": 970028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e90e13e03d2121354301953488cddd92b4868bbc10fb3e12c4d15b9cbf01f857" } } ], "extra": [ 1, 209, 177, 177, 220, 94, 199, 246, 62, 144, 16, 98, 153, 1, 188, 105, 225, 33, 212, 149, 37, 74, 122, 174, 2, 242, 71, 45, 38, 97, 73, 1, 21, 2, 17, 0, 0, 0, 2, 73, 161, 133, 187, 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