Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e5001904e2ed6994000c96be8211f5948da06059c1e911cac52d02ef6f26d7a

Tx prefix hash: 226c88358dfe8c2140b1f38dd858dfdf5fa12395c71326417e48c4a858d5c8e4
Tx public key: 10f70b06d13d1db625e5f0ca39d07bc7d3d22743562fd5b7cf0a6dc6dae5c783
Timestamp: 1626859264 Timestamp [UCT]: 2021-07-21 09:21:04 Age [y:d:h:m:s]: 04:106:22:48:03
Block: 298134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106528 RingCT/type: yes/0
Extra: 0110f70b06d13d1db625e5f0ca39d07bc7d3d22743562fd5b7cf0a6dc6dae5c783021100000006a272b9cb000000000000000000

1 output(s) for total of 63.118808189000 dcy

stealth address amount amount idx
00: 61a96eba7dd7d6069b0b7c59759275ed975072291beb97ea768d78feecd0413a 63.118808189000 623893 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": 298144, "vin": [ { "gen": { "height": 298134 } } ], "vout": [ { "amount": 63118808189, "target": { "key": "61a96eba7dd7d6069b0b7c59759275ed975072291beb97ea768d78feecd0413a" } } ], "extra": [ 1, 16, 247, 11, 6, 209, 61, 29, 182, 37, 229, 240, 202, 57, 208, 123, 199, 211, 210, 39, 67, 86, 47, 213, 183, 207, 10, 109, 198, 218, 229, 199, 131, 2, 17, 0, 0, 0, 6, 162, 114, 185, 203, 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