Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c64d5ccf42393e14c26ce8c7de5ac18646dd2dca478df8bbf7607cbaccd9c9f

Tx prefix hash: 57a79eea094fdb88fdc94d5e0dcb55aa56f432ec7697300b35cce520340d22a9
Tx public key: 5e883fbe3c78c0cd33e6ccd65cb18af2910569a7e98595a7fae13c62d6969e84
Timestamp: 1714632254 Timestamp [UCT]: 2024-05-02 06:44:14 Age [y:d:h:m:s]: 01:022:15:42:27
Block: 1013061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 277133 RingCT/type: yes/0
Extra: 015e883fbe3c78c0cd33e6ccd65cb18af2910569a7e98595a7fae13c62d6969e8402110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 354832f4f7a938143af39afac3698331a8a08511e9d002d9d30869b57c73e832 0.600000000000 1475778 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": 1013071, "vin": [ { "gen": { "height": 1013061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "354832f4f7a938143af39afac3698331a8a08511e9d002d9d30869b57c73e832" } } ], "extra": [ 1, 94, 136, 63, 190, 60, 120, 192, 205, 51, 230, 204, 214, 92, 177, 138, 242, 145, 5, 105, 167, 233, 133, 149, 167, 250, 225, 60, 98, 214, 150, 158, 132, 2, 17, 0, 0, 0, 6, 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