Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 828d10ac39ffc03a8cb7768ae373af9fd5be9af358b571b3a9adeedbedb5aa72

Tx prefix hash: 62c37ae88d538fc93cdebd82e05365253cc5766478043955628415d1c9c76293
Tx public key: e891b8b07ffd0238922b4dce385c597df3b9872cfe4b3e0a32fcae629c9ec5f0
Timestamp: 1723886776 Timestamp [UCT]: 2024-08-17 09:26:16 Age [y:d:h:m:s]: 00:244:05:55:51
Block: 1089787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174444 RingCT/type: yes/0
Extra: 01e891b8b07ffd0238922b4dce385c597df3b9872cfe4b3e0a32fcae629c9ec5f002110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc916dbc452def00b2ec5a91f399519713747ea422c39fecbeb19cd87edf2a87 0.600000000000 1564410 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": 1089797, "vin": [ { "gen": { "height": 1089787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc916dbc452def00b2ec5a91f399519713747ea422c39fecbeb19cd87edf2a87" } } ], "extra": [ 1, 232, 145, 184, 176, 127, 253, 2, 56, 146, 43, 77, 206, 56, 92, 89, 125, 243, 185, 135, 44, 254, 75, 62, 10, 50, 252, 174, 98, 156, 158, 197, 240, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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