Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17040753fa333cc54abd286424b9d20e2696dfd67024fcc8d4e0b07f0860d9a4

Tx prefix hash: d478576939353a4f78d1c16656c21eebfb06070839a1a0efd91a3dc73f40da7e
Tx public key: 7a5caeb743c8cbd5b0614c040f6a17f62ebfdf77c694bf688950f6cf35e646a6
Timestamp: 1752325007 Timestamp [UCT]: 2025-07-12 12:56:47 Age [y:d:h:m:s]: 00:131:23:32:05
Block: 1323917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93026 RingCT/type: yes/0
Extra: 017a5caeb743c8cbd5b0614c040f6a17f62ebfdf77c694bf688950f6cf35e646a60211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 066098c971523b7b25c76303746031c1838e547d6b17bf10319df5d1b6e45c80 0.600000000000 1811658 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": 1323927, "vin": [ { "gen": { "height": 1323917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "066098c971523b7b25c76303746031c1838e547d6b17bf10319df5d1b6e45c80" } } ], "extra": [ 1, 122, 92, 174, 183, 67, 200, 203, 213, 176, 97, 76, 4, 15, 106, 23, 246, 46, 191, 223, 119, 198, 148, 191, 104, 137, 80, 246, 207, 53, 230, 70, 166, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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