Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 965aba3dd2dedb179704de3b7968255230823e37f6126d1aa0db3bf6362f81b5

Tx prefix hash: df1845fc6619e4b1f86d9d84a9b452853691e152f7dadb16505b54ff7b10ffa2
Tx public key: 06c788e5d32c0f43e980009f0e7d6b80ea7ad26817303aec576c927633306098
Timestamp: 1762686242 Timestamp [UCT]: 2025-11-09 11:04:02 Age [y:d:h:m:s]: 00:057:13:49:23
Block: 1408324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41238 RingCT/type: yes/0
Extra: 0106c788e5d32c0f43e980009f0e7d6b80ea7ad26817303aec576c927633306098021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81ade8a3456754dbbf6c2f760e7d5de23285448d7c1cfcaeaf3f4e2fd8f0a211 0.600000000000 1896753 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": 1408334, "vin": [ { "gen": { "height": 1408324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81ade8a3456754dbbf6c2f760e7d5de23285448d7c1cfcaeaf3f4e2fd8f0a211" } } ], "extra": [ 1, 6, 199, 136, 229, 211, 44, 15, 67, 233, 128, 0, 159, 14, 125, 107, 128, 234, 122, 210, 104, 23, 48, 58, 236, 87, 108, 146, 118, 51, 48, 96, 152, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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