Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5a46dc59147cc444c3d8223d21b3d6d2537174ee3339b3befbc7088bffc0aad

Tx prefix hash: 136b0499c3d76d46d46ed59af39ab5f35b2ef2b66de04e71fa569f3b3e59643d
Tx public key: 6d8d09a1cf3e4198c6c65dcbe21f1db972cc730370aaf8c96a128f2d6d73e2c5
Timestamp: 1709988034 Timestamp [UCT]: 2024-03-09 12:40:34 Age [y:d:h:m:s]: 00:307:02:42:08
Block: 974560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219838 RingCT/type: yes/0
Extra: 016d8d09a1cf3e4198c6c65dcbe21f1db972cc730370aaf8c96a128f2d6d73e2c502110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22f36c8a0ca5a944ae0de5a8db402a571b04a5b7788731b712748104318b72b3 0.600000000000 1434519 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": 974570, "vin": [ { "gen": { "height": 974560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22f36c8a0ca5a944ae0de5a8db402a571b04a5b7788731b712748104318b72b3" } } ], "extra": [ 1, 109, 141, 9, 161, 207, 62, 65, 152, 198, 198, 93, 203, 226, 31, 29, 185, 114, 204, 115, 3, 112, 170, 248, 201, 106, 18, 143, 45, 109, 115, 226, 197, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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