Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8c0edd97ae533c4152f10fc0e606b0dde04d929a13f0c74868d23b352056deb

Tx prefix hash: a3ca7580ef31bcaba8d09d5ddbf2dbc24581a985e65c941b3c8caa047eb91924
Tx public key: 2799d50b8d7414dd633bf3d5a797052b22ad283c1da291119124ea843b1d2dd0
Timestamp: 1719768787 Timestamp [UCT]: 2024-06-30 17:33:07 Age [y:d:h:m:s]: 00:276:20:34:27
Block: 1055631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197823 RingCT/type: yes/0
Extra: 012799d50b8d7414dd633bf3d5a797052b22ad283c1da291119124ea843b1d2dd00211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea608091c011d7f61a5604b67f52939e4a11feb6632cfee5f317dc72eeb8a021 0.600000000000 1526036 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": 1055641, "vin": [ { "gen": { "height": 1055631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea608091c011d7f61a5604b67f52939e4a11feb6632cfee5f317dc72eeb8a021" } } ], "extra": [ 1, 39, 153, 213, 11, 141, 116, 20, 221, 99, 59, 243, 213, 167, 151, 5, 43, 34, 173, 40, 60, 29, 162, 145, 17, 145, 36, 234, 132, 59, 29, 45, 208, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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