Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4ae35ef30bc861176aca1b889a8e0e56de36cda7797286e87830c706fbbfd2d

Tx prefix hash: b67bada15bc4f4a9d21dd37c56583429459e3acc1e7db0a6ec79b0a95fba25c5
Tx public key: 15b4efa548b708cc05b54db1dc24613c0a390ce5aeacfe18cfea7ba3d8caef0a
Timestamp: 1757609302 Timestamp [UCT]: 2025-09-11 16:48:22 Age [y:d:h:m:s]: 00:060:06:34:16
Block: 1366235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43168 RingCT/type: yes/0
Extra: 0115b4efa548b708cc05b54db1dc24613c0a390ce5aeacfe18cfea7ba3d8caef0a021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 291f9447c51b099f0fdcfcdd7655b1ba6e9f144f496f2cd76031a773c50ac544 0.600000000000 1854274 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": 1366245, "vin": [ { "gen": { "height": 1366235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "291f9447c51b099f0fdcfcdd7655b1ba6e9f144f496f2cd76031a773c50ac544" } } ], "extra": [ 1, 21, 180, 239, 165, 72, 183, 8, 204, 5, 181, 77, 177, 220, 36, 97, 60, 10, 57, 12, 229, 174, 172, 254, 24, 207, 234, 123, 163, 216, 202, 239, 10, 2, 17, 0, 0, 0, 1, 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