Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df7fe6ed9d3a81026a3cc0365bd9b5ddcb43bce5bf95ba1970e1e34e3230ab71

Tx prefix hash: 393cdc1ff37da8aeaa0bd468a8747708bcd3058bd69690f3b2c5c18e1107b6b4
Tx public key: 7545c6ebd5fe87acfdc1350a8bd81bd3dfad2bc2540702c897293c35516b87e7
Timestamp: 1759926364 Timestamp [UCT]: 2025-10-08 12:26:04 Age [y:d:h:m:s]: 00:113:17:51:58
Block: 1385438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81281 RingCT/type: yes/0
Extra: 017545c6ebd5fe87acfdc1350a8bd81bd3dfad2bc2540702c897293c35516b87e7021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85742c0e8bd8a312ee400e121e0fb8f3c88ac414796bf1af0a38b2f471e5b896 0.600000000000 1873601 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": 1385448, "vin": [ { "gen": { "height": 1385438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85742c0e8bd8a312ee400e121e0fb8f3c88ac414796bf1af0a38b2f471e5b896" } } ], "extra": [ 1, 117, 69, 198, 235, 213, 254, 135, 172, 253, 193, 53, 10, 139, 216, 27, 211, 223, 173, 43, 194, 84, 7, 2, 200, 151, 41, 60, 53, 81, 107, 135, 231, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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