Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 213c63340486651f2774e94fc34c412c402ff8615922962a9f5d9ff11a298572

Tx prefix hash: 9b4967c115a9342f8397f31fecf4561dc045c96f3c6f9c63461193a414bb0ff7
Tx public key: 1e3df457a940e680116886e9bb374a2a5b6810d25fe53eec9262c6a3cfac8166
Timestamp: 1657212320 Timestamp [UCT]: 2022-07-07 16:45:20 Age [y:d:h:m:s]: 03:116:08:04:23
Block: 538714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 862873 RingCT/type: yes/0
Extra: 011e3df457a940e680116886e9bb374a2a5b6810d25fe53eec9262c6a3cfac81660211000000014da16a3a000000000000000000

1 output(s) for total of 10.069711683000 dcy

stealth address amount amount idx
00: 69dcb2448cce6847c5cb437261cdb47bdd8bf9b5e2883e66717c492ea0f05ab5 10.069711683000 968747 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": 538724, "vin": [ { "gen": { "height": 538714 } } ], "vout": [ { "amount": 10069711683, "target": { "key": "69dcb2448cce6847c5cb437261cdb47bdd8bf9b5e2883e66717c492ea0f05ab5" } } ], "extra": [ 1, 30, 61, 244, 87, 169, 64, 230, 128, 17, 104, 134, 233, 187, 55, 74, 42, 91, 104, 16, 210, 95, 229, 62, 236, 146, 98, 198, 163, 207, 172, 129, 102, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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