Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b8ee62fa8f9a8fa2c81d725d6d6bfd9c3c4e2efc7367ecd789f6dc05ba0307d

Tx prefix hash: 43d0143fe0a6627ef6f9b01dba9520674cd962c47dc4c6af79460165934f1b22
Tx public key: 7292415ad7b83a88e94c484a66fa71f3e10b5731854cd090ccf6be8127d90fd1
Timestamp: 1726696680 Timestamp [UCT]: 2024-09-18 21:58:00 Age [y:d:h:m:s]: 01:076:00:21:38
Block: 1113070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312771 RingCT/type: yes/0
Extra: 017292415ad7b83a88e94c484a66fa71f3e10b5731854cd090ccf6be8127d90fd102110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56b63f9f9b28f73f6c78bb326feba876a73386a1f1a54993f9e7209e5e4cc49c 0.600000000000 1592613 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": 1113080, "vin": [ { "gen": { "height": 1113070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56b63f9f9b28f73f6c78bb326feba876a73386a1f1a54993f9e7209e5e4cc49c" } } ], "extra": [ 1, 114, 146, 65, 90, 215, 184, 58, 136, 233, 76, 72, 74, 102, 250, 113, 243, 225, 11, 87, 49, 133, 76, 208, 144, 204, 246, 190, 129, 39, 217, 15, 209, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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