Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fac7d6d7e4cd2474e481c3d718f1953ea7ecf941089cad0a3379edcc8b07ab39

Tx prefix hash: e62cfcadd44528bdc6d0329a9308bb4ed689585b019607c08b80f431a2688e0b
Tx public key: df18ad294b68bd4d172719d22f92abf37c5ff02de28d19a9f472c8d73597158f
Timestamp: 1743774709 Timestamp [UTC]: 2025-04-04 13:51:49 Age [y:d:h:m:s]: 01:227:14:29:46
Block: 1254161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426722 RingCT/type: yes/0
Extra: 01df18ad294b68bd4d172719d22f92abf37c5ff02de28d19a9f472c8d73597158f0211000000024060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dd8fbe7a2d45ee39be9298dfa62a1f934206be0ab8657175f138c793676d66e0 0.000600000000 1741242 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": 1254171, "vin": [ { "gen": { "height": 1254161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd8fbe7a2d45ee39be9298dfa62a1f934206be0ab8657175f138c793676d66e0" } } ], "extra": [ 1, 223, 24, 173, 41, 75, 104, 189, 77, 23, 39, 25, 210, 47, 146, 171, 243, 124, 95, 240, 45, 226, 141, 25, 169, 244, 114, 200, 215, 53, 151, 21, 143, 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: