Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e9cc1c27d5ecc3dc1e4998e1b27df31bb1da51ebcfecd76b99f270ecf93d45c

Tx prefix hash: 36ae31dd365f721f606ab91a51222db8dbbe48c995a09ee0b67f8abeef933c4e
Tx public key: de97d066c6b4272673ebbab8151d49c6173de1750d5cb825fdc7aa5b48d212d9
Timestamp: 1759549404 Timestamp [UCT]: 2025-10-04 03:43:24 Age [y:d:h:m:s]: 00:111:18:46:31
Block: 1382316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79869 RingCT/type: yes/0
Extra: 01de97d066c6b4272673ebbab8151d49c6173de1750d5cb825fdc7aa5b48d212d902110000000397baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b2aef491bdfd530411ce54430546d794f0d3c87bbb95f55827a824a5fab3401 0.600000000000 1870451 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": 1382326, "vin": [ { "gen": { "height": 1382316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b2aef491bdfd530411ce54430546d794f0d3c87bbb95f55827a824a5fab3401" } } ], "extra": [ 1, 222, 151, 208, 102, 198, 180, 39, 38, 115, 235, 186, 184, 21, 29, 73, 198, 23, 61, 225, 117, 13, 92, 184, 37, 253, 199, 170, 91, 72, 210, 18, 217, 2, 17, 0, 0, 0, 3, 151, 186, 249, 34, 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