Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b2396c85e49551c39c204a51fe7e71b4d6d23b1f5803b8157e0ec9205458636

Tx prefix hash: 08b9b5b004091697e73bc04da6603d6fb84f273ccaa7dd9a2bd5e053bcab70b5
Tx public key: 06121a156c9a67dbc2d8c79f4ade4ae9df2844417da2582f85eac45e182297c8
Timestamp: 1713599642 Timestamp [UCT]: 2024-04-20 07:54:02 Age [y:d:h:m:s]: 00:218:20:43:22
Block: 1004474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156686 RingCT/type: yes/0
Extra: 0106121a156c9a67dbc2d8c79f4ade4ae9df2844417da2582f85eac45e182297c80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51d1f180f0cbc168654b570f80b2bfa6fd3b11e419841611f761197732224ef7 0.600000000000 1465042 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": 1004484, "vin": [ { "gen": { "height": 1004474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51d1f180f0cbc168654b570f80b2bfa6fd3b11e419841611f761197732224ef7" } } ], "extra": [ 1, 6, 18, 26, 21, 108, 154, 103, 219, 194, 216, 199, 159, 74, 222, 74, 233, 223, 40, 68, 65, 125, 162, 88, 47, 133, 234, 196, 94, 24, 34, 151, 200, 2, 17, 0, 0, 0, 1, 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