Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 442be6dff00034fb2a9f59fdb37dd1a3334cd6b1805b1b40c94c29b02dc59fca

Tx prefix hash: 145837c9ede250e8636ecfc54d2f17d19676fb208195d3f8b1334384163e7bcd
Tx public key: c919aa522e91c19a9284def8fc7fc4822abf6cde9201a435a150cc30cdf2eb79
Timestamp: 1755926824 Timestamp [UCT]: 2025-08-23 05:27:04 Age [y:d:h:m:s]: 00:090:09:10:35
Block: 1352480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64530 RingCT/type: yes/0
Extra: 01c919aa522e91c19a9284def8fc7fc4822abf6cde9201a435a150cc30cdf2eb79021100000005ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c011ba4a6b4342b2af670f0a8d2ba286d613221f923c7c03d3733c0cced6af0b 0.600000000000 1840445 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": 1352490, "vin": [ { "gen": { "height": 1352480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c011ba4a6b4342b2af670f0a8d2ba286d613221f923c7c03d3733c0cced6af0b" } } ], "extra": [ 1, 201, 25, 170, 82, 46, 145, 193, 154, 146, 132, 222, 248, 252, 127, 196, 130, 42, 191, 108, 222, 146, 1, 164, 53, 161, 80, 204, 48, 205, 242, 235, 121, 2, 17, 0, 0, 0, 5, 173, 121, 72, 208, 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