Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 939b639404bdaa1feef96e88d89f91afc21e490ba8941ff47ca36e4d94b80474

Tx prefix hash: 0dba0d19af919b82cc1b4c8fde6710ea33cfd2fc37bf594e4eee8df94992d139
Tx public key: 44ef2b3a65a9efcb834240db7f75812fb997adcc4ea452d1caa89d136ae4cdfd
Timestamp: 1763188055 Timestamp [UCT]: 2025-11-15 06:27:35 Age [y:d:h:m:s]: 00:051:17:52:00
Block: 1412477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37071 RingCT/type: yes/0
Extra: 0144ef2b3a65a9efcb834240db7f75812fb997adcc4ea452d1caa89d136ae4cdfd02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f32a26fcd08bcea0d2e11c6b75e5634dbcd9f6d28f479e7f39f77c1dc189896 0.600000000000 1900946 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": 1412487, "vin": [ { "gen": { "height": 1412477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f32a26fcd08bcea0d2e11c6b75e5634dbcd9f6d28f479e7f39f77c1dc189896" } } ], "extra": [ 1, 68, 239, 43, 58, 101, 169, 239, 203, 131, 66, 64, 219, 127, 117, 129, 47, 185, 151, 173, 204, 78, 164, 82, 209, 202, 168, 157, 19, 106, 228, 205, 253, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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