Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 292158c9bcf19b13149a3583d5864b29f582768a383c4c0e17484f95d96f3d44

Tx prefix hash: fc594a6d1867dc0e3c2bf679c5ad197bf700a628222d7a5a3a9d8ba95d0c000c
Tx public key: c2fa6e7732c330a891890ce9230ae7d7e3174b0c9fccf69332e6770c11c583dd
Timestamp: 1737343945 Timestamp [UCT]: 2025-01-20 03:32:25 Age [y:d:h:m:s]: 00:149:20:17:37
Block: 1201148 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106828 RingCT/type: yes/0
Extra: 01c2fa6e7732c330a891890ce9230ae7d7e3174b0c9fccf69332e6770c11c583dd0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f96235400a94d213fb550bb8c8daa600373c38902ff917e0051db54f719628b 0.600000000000 1687797 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": 1201158, "vin": [ { "gen": { "height": 1201148 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f96235400a94d213fb550bb8c8daa600373c38902ff917e0051db54f719628b" } } ], "extra": [ 1, 194, 250, 110, 119, 50, 195, 48, 168, 145, 137, 12, 233, 35, 10, 231, 215, 227, 23, 75, 12, 159, 204, 246, 147, 50, 230, 119, 12, 17, 197, 131, 221, 2, 17, 0, 0, 0, 5, 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