Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d8f563f6d53ff519d3941f9640096d560d9a56fe789b1c67536d6f01b1c3d49

Tx prefix hash: f40386c58753ce046591470c7cc1bbec010b06edcea1536c0b714650b3687153
Tx public key: 176a3175adc90e02a73c6a75c1fb19bf46a93a6b0d14ff8fef1c7144c89a501b
Timestamp: 1751124478 Timestamp [UCT]: 2025-06-28 15:27:58 Age [y:d:h:m:s]: 00:145:21:51:40
Block: 1314603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102362 RingCT/type: yes/0
Extra: 01176a3175adc90e02a73c6a75c1fb19bf46a93a6b0d14ff8fef1c7144c89a501b021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38d9f37eb089a1b07464eec846fc4ce9d55e8829ec70ce773529ffa8a081bfca 0.600000000000 1802252 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": 1314613, "vin": [ { "gen": { "height": 1314603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38d9f37eb089a1b07464eec846fc4ce9d55e8829ec70ce773529ffa8a081bfca" } } ], "extra": [ 1, 23, 106, 49, 117, 173, 201, 14, 2, 167, 60, 106, 117, 193, 251, 25, 191, 70, 169, 58, 107, 13, 20, 255, 143, 239, 28, 113, 68, 200, 154, 80, 27, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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