Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b39a9620b1f2783a7a7226f0257fc91e98e59202cf3d47855edc4b4aeae8639

Tx prefix hash: 2dfe6aa1a67a570e73b5a3410083600b8f9153818960e510d67872eafde129ba
Tx public key: 805333ef614db1cbc49e82ab50928a162cacc6d198b883a4dd11f7f1c1d1f404
Timestamp: 1736712527 Timestamp [UCT]: 2025-01-12 20:08:47 Age [y:d:h:m:s]: 00:337:03:44:20
Block: 1195965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238511 RingCT/type: yes/0
Extra: 01805333ef614db1cbc49e82ab50928a162cacc6d198b883a4dd11f7f1c1d1f4040211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db385bc97eb488d20635e01b7944814d4cf9edd5afcd791f95207ab9d02f4feb 0.600000000000 1682560 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": 1195975, "vin": [ { "gen": { "height": 1195965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db385bc97eb488d20635e01b7944814d4cf9edd5afcd791f95207ab9d02f4feb" } } ], "extra": [ 1, 128, 83, 51, 239, 97, 77, 177, 203, 196, 158, 130, 171, 80, 146, 138, 22, 44, 172, 198, 209, 152, 184, 131, 164, 221, 17, 247, 241, 193, 209, 244, 4, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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