Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3f3a0f8317a0f95cd11401afeffb6c71fb4129fcb47cb22e1ca4d6e66f0fe64

Tx prefix hash: 6641e1c27e1bc69deed00a68cd07248a73d0e37aaab8e80e356ad89cc6da3570
Tx public key: 610ae93591e6b544c467a66c577a280e0b97b8b64fb82484a26564d8b2372328
Timestamp: 1765562687 Timestamp [UCT]: 2025-12-12 18:04:47 Age [y:d:h:m:s]: 00:041:12:36:31
Block: 1432163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29587 RingCT/type: yes/0
Extra: 01610ae93591e6b544c467a66c577a280e0b97b8b64fb82484a26564d8b237232802110000000a70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50bb9c0cffa48fb081fb40b2b341446d31b95f7bb97a659f5d5ee56c122a1d23 0.600000000000 1920942 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": 1432173, "vin": [ { "gen": { "height": 1432163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50bb9c0cffa48fb081fb40b2b341446d31b95f7bb97a659f5d5ee56c122a1d23" } } ], "extra": [ 1, 97, 10, 233, 53, 145, 230, 181, 68, 196, 103, 166, 108, 87, 122, 40, 14, 11, 151, 184, 182, 79, 184, 36, 132, 162, 101, 100, 216, 178, 55, 35, 40, 2, 17, 0, 0, 0, 10, 112, 96, 157, 3, 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