Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef3e3097bab8e8815dbfb71aa7343e81ecb9f7f9a5a047596f01937b79abd797

Tx prefix hash: e86e4980e3e08808916c08bc40325f672426b7a81dbc1eec9946cbcc554c93f4
Tx public key: 4aa2a66e93b416f78790c1b2e49500651abc4d2a72e8265dc74cfa66779ee307
Timestamp: 1743755052 Timestamp [UTC]: 2025-04-04 08:24:12 Age [y:d:h:m:s]: 01:229:05:38:33
Block: 1254000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427941 RingCT/type: yes/0
Extra: 014aa2a66e93b416f78790c1b2e49500651abc4d2a72e8265dc74cfa66779ee3070211000000024060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 890cf2c820640033fff0a7d7994ae198fd845a539fa8a1ccfd534ab7f14368c3 0.000600000000 1741081 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": 1254010, "vin": [ { "gen": { "height": 1254000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "890cf2c820640033fff0a7d7994ae198fd845a539fa8a1ccfd534ab7f14368c3" } } ], "extra": [ 1, 74, 162, 166, 110, 147, 180, 22, 247, 135, 144, 193, 178, 228, 149, 0, 101, 26, 188, 77, 42, 114, 232, 38, 93, 199, 76, 250, 102, 119, 158, 227, 7, 2, 17, 0, 0, 0, 2, 64, 96, 246, 210, 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: