Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 292e87d9ff8510fcc7dc06301001f49dd435b7d9da473f5367f2605507090fed

Tx prefix hash: eb23f828306e58b106ea16a3de7773c79834569f10ce9738c79b523ee713a8f7
Tx public key: 0af32f9fd3de2863cc5d5171894641e1e2cc5926919e4db80d961d84287f945a
Timestamp: 1764274596 Timestamp [UCT]: 2025-11-27 20:16:36 Age [y:d:h:m:s]: 00:041:23:34:33
Block: 1421491 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30064 RingCT/type: yes/0
Extra: 010af32f9fd3de2863cc5d5171894641e1e2cc5926919e4db80d961d84287f945a021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c9b3aa80dc0bca4d212e1aa0cbc0cc6715d4ef77690314d6e10470e2ebe4de0 0.600000000000 1910048 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": 1421501, "vin": [ { "gen": { "height": 1421491 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c9b3aa80dc0bca4d212e1aa0cbc0cc6715d4ef77690314d6e10470e2ebe4de0" } } ], "extra": [ 1, 10, 243, 47, 159, 211, 222, 40, 99, 204, 93, 81, 113, 137, 70, 65, 225, 226, 204, 89, 38, 145, 158, 77, 184, 13, 150, 29, 132, 40, 127, 148, 90, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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