Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d83ae05974250ffa8c0ef618d4e5ba7e355309b5d78416d14b0e97232463055e

Tx prefix hash: 3bb3fe74150cebeca400ec6223e0f546473c4e8fbbe84597d1ee58882cec1446
Tx public key: fc305f4f4a7f714e0c1f8391ecc6b09c220a3e8ec0bc10fb33d50ddacbb84857
Timestamp: 1755530775 Timestamp [UCT]: 2025-08-18 15:26:15 Age [y:d:h:m:s]: 00:089:05:22:33
Block: 1349256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63651 RingCT/type: yes/0
Extra: 01fc305f4f4a7f714e0c1f8391ecc6b09c220a3e8ec0bc10fb33d50ddacbb8485702110000000cb2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 133e3d261f3efe7c64fdb60db2dae449e50a964eae13d3943311a0cc11ebaf3c 0.600000000000 1837187 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": 1349266, "vin": [ { "gen": { "height": 1349256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "133e3d261f3efe7c64fdb60db2dae449e50a964eae13d3943311a0cc11ebaf3c" } } ], "extra": [ 1, 252, 48, 95, 79, 74, 127, 113, 78, 12, 31, 131, 145, 236, 198, 176, 156, 34, 10, 62, 142, 192, 188, 16, 251, 51, 213, 13, 218, 203, 184, 72, 87, 2, 17, 0, 0, 0, 12, 178, 247, 132, 196, 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