Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c639a9b5fab4b97bfa1a3e06b3e051bd9a2089efc326262f69a91e4e8881a893

Tx prefix hash: 8438342d4c07a619524295a955116fa785341e358c20951cb3d75aa841b1555d
Tx public key: df1fe7628fcc054978fcec8d6ccfea7197f61ad75273fa49b3e717e763a5c487
Timestamp: 1724799723 Timestamp [UCT]: 2024-08-27 23:02:03 Age [y:d:h:m:s]: 01:156:05:08:01
Block: 1097337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370027 RingCT/type: yes/0
Extra: 01df1fe7628fcc054978fcec8d6ccfea7197f61ad75273fa49b3e717e763a5c487021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46b774acd854221615170e861846861e78a0e0207289ae61135b1c5c818a8207 0.600000000000 1572728 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": 1097347, "vin": [ { "gen": { "height": 1097337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46b774acd854221615170e861846861e78a0e0207289ae61135b1c5c818a8207" } } ], "extra": [ 1, 223, 31, 231, 98, 143, 204, 5, 73, 120, 252, 236, 141, 108, 207, 234, 113, 151, 246, 26, 215, 82, 115, 250, 73, 179, 231, 23, 231, 99, 165, 196, 135, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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