Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0204df3784d5c1c2e82993edfb36663c1af7bf1526b8a5084aaf0d42126f6298

Tx prefix hash: 42b4dadfeb80c4e074f964200e53c1f4682e5c8782fdf6b876c18d8a82a136d9
Tx public key: 11aaa9c71896fb994b5c210f1830c182ed44ec6c3c694c361095a729699724ba
Timestamp: 1742390946 Timestamp [UCT]: 2025-03-19 13:29:06 Age [y:d:h:m:s]: 00:320:01:01:23
Block: 1242737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226375 RingCT/type: yes/0
Extra: 0111aaa9c71896fb994b5c210f1830c182ed44ec6c3c694c361095a729699724ba0211000000041db82ba9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07fde2663778456ad20bfa4c9f4c5cd8251cacf678a71163d99b00dc1c12de2d 0.600000000000 1729712 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": 1242747, "vin": [ { "gen": { "height": 1242737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07fde2663778456ad20bfa4c9f4c5cd8251cacf678a71163d99b00dc1c12de2d" } } ], "extra": [ 1, 17, 170, 169, 199, 24, 150, 251, 153, 75, 92, 33, 15, 24, 48, 193, 130, 237, 68, 236, 108, 60, 105, 76, 54, 16, 149, 167, 41, 105, 151, 36, 186, 2, 17, 0, 0, 0, 4, 29, 184, 43, 169, 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