Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad300fb832cd556a12c368fed4a873db35e4e6b9c1f560053fdf606c4f825f17

Tx prefix hash: 2f92df72b812c2513343e83da851574133f60011d208083efede405e555f9790
Tx public key: 0cdc4c3e321e595252dc5345608182eff8237a83461f5fca273b253e1fcab74b
Timestamp: 1712040868 Timestamp [UCT]: 2024-04-02 06:54:28 Age [y:d:h:m:s]: 00:290:06:55:14
Block: 991543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207809 RingCT/type: yes/0
Extra: 010cdc4c3e321e595252dc5345608182eff8237a83461f5fca273b253e1fcab74b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2615c7d3f8dcc9f9d6a612c7e464e55ad92e50d43492064b7a3b388e6aca3556 0.600000000000 1451879 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": 991553, "vin": [ { "gen": { "height": 991543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2615c7d3f8dcc9f9d6a612c7e464e55ad92e50d43492064b7a3b388e6aca3556" } } ], "extra": [ 1, 12, 220, 76, 62, 50, 30, 89, 82, 82, 220, 83, 69, 96, 129, 130, 239, 248, 35, 122, 131, 70, 31, 95, 202, 39, 59, 37, 62, 31, 202, 183, 75, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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