Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f396e732d3a40868fb70d13b761d2d078adcf8d31a460f81be35e9d927bd55c

Tx prefix hash: 37b8aeed66be2909ff37bc3351f6357d2e82b836daccf8b78296c3cfe0a665a2
Tx public key: 67707a8b222fafa3f53ce395defca967a4dea9fec866570cc1efd8fe42550341
Timestamp: 1744378067 Timestamp [UTC]: 2025-04-11 13:27:47 Age [y:d:h:m:s]: 01:131:01:55:59
Block: 1259168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358392 RingCT/type: yes/0
Extra: 0167707a8b222fafa3f53ce395defca967a4dea9fec866570cc1efd8fe425503410211000000026c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 239a368cce3b301e834a1544ed5de8ff7ac40c1d05ca92915ad3f4e9ae9a569a 0.000600000000 1746307 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 dinastycoin-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": 1259178, "vin": [ { "gen": { "height": 1259168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "239a368cce3b301e834a1544ed5de8ff7ac40c1d05ca92915ad3f4e9ae9a569a" } } ], "extra": [ 1, 103, 112, 122, 139, 34, 47, 175, 163, 245, 60, 227, 149, 222, 252, 169, 103, 164, 222, 169, 254, 200, 102, 87, 12, 193, 239, 216, 254, 66, 85, 3, 65, 2, 17, 0, 0, 0, 2, 108, 152, 170, 61, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: