Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d24837ecd4c834a5d07eca2c85276bfc53f60be080dc09e80321ff47622a0dce

Tx prefix hash: 1bc0828988f09d6ca57920bf06d2f3ea4fe2bf7e1e5b03031aa5b2ea6f1e6d9d
Tx public key: 9def7c6ff00011e7be1fdbeb6267d68707cae3fc94fe03a8974a476f1eccef86
Timestamp: 1756028111 Timestamp [UCT]: 2025-08-24 09:35:11 Age [y:d:h:m:s]: 00:094:04:57:31
Block: 1353329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67265 RingCT/type: yes/0
Extra: 019def7c6ff00011e7be1fdbeb6267d68707cae3fc94fe03a8974a476f1eccef860211000000062609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 149839501cfc075c3deeb5a0d9e7e9d4930812e1aaa871686523ceed4d3fa917 0.600000000000 1841304 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": 1353339, "vin": [ { "gen": { "height": 1353329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "149839501cfc075c3deeb5a0d9e7e9d4930812e1aaa871686523ceed4d3fa917" } } ], "extra": [ 1, 157, 239, 124, 111, 240, 0, 17, 231, 190, 31, 219, 235, 98, 103, 214, 135, 7, 202, 227, 252, 148, 254, 3, 168, 151, 74, 71, 111, 30, 204, 239, 134, 2, 17, 0, 0, 0, 6, 38, 9, 179, 160, 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