Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ba38caf9892c7d1594b137a81ad6bfcc657a0b0f55ffc8a32dcfa9e71943955

Tx prefix hash: 804793559531b06cc84e6ef0806c6b560c2a5116d31abd512d21ec3de9106447
Tx public key: 2909eb4e5a315e9fcaadab8869b4665fde6f7efedf37fffcce1ed62a96897b75
Timestamp: 1746296947 Timestamp [UTC]: 2025-05-03 18:29:07 Age [y:d:h:m:s]: 01:199:01:37:59
Block: 1275050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406306 RingCT/type: yes/0
Extra: 012909eb4e5a315e9fcaadab8869b4665fde6f7efedf37fffcce1ed62a96897b7502110000000601491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a1131c171d18bca41f2da23be716f7dda4781c201a5245e1839687d8df0dd075 0.000600000000 1762355 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": 1275060, "vin": [ { "gen": { "height": 1275050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1131c171d18bca41f2da23be716f7dda4781c201a5245e1839687d8df0dd075" } } ], "extra": [ 1, 41, 9, 235, 78, 90, 49, 94, 159, 202, 173, 171, 136, 105, 180, 102, 95, 222, 111, 126, 254, 223, 55, 255, 252, 206, 30, 214, 42, 150, 137, 123, 117, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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: