Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e3f9ea36b2328ddcfba94b3a2e575ba30a97489b113cfabc4476b3fa26b9e9e

Tx prefix hash: b564b068c207b1207a74e1e5c244f5430ed83600337246e4483d2efaefe13b24
Tx public key: 08499f0c192413a7b8822e3ae9f4c2a363ce001dd642fda0d1a6871932e88b7b
Timestamp: 1745145179 Timestamp [UTC]: 2025-04-20 10:32:59 Age [y:d:h:m:s]: 01:099:07:12:14
Block: 1265509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334938 RingCT/type: yes/0
Extra: 0108499f0c192413a7b8822e3ae9f4c2a363ce001dd642fda0d1a6871932e88b7b0211000000126c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fb1f3ff48d2898ea085c3dbe58341cda059f59de6fce63758a5cedb9bdb10a13 0.000600000000 1752720 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": 1265519, "vin": [ { "gen": { "height": 1265509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb1f3ff48d2898ea085c3dbe58341cda059f59de6fce63758a5cedb9bdb10a13" } } ], "extra": [ 1, 8, 73, 159, 12, 25, 36, 19, 167, 184, 130, 46, 58, 233, 244, 194, 163, 99, 206, 0, 29, 214, 66, 253, 160, 209, 166, 135, 25, 50, 232, 139, 123, 2, 17, 0, 0, 0, 18, 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: