Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3bb8784a0b65fae1f6db81cc4e733a2b4ffac1a0e3c3a66fe66311379bcd8b2

Tx prefix hash: 18c832c8ac2c97768fe1ac5f690bf31568546595a2f8e129b121abf099a25cc8
Tx public key: 2a6e5a52e5d2bde1218373f4ff7bea46b91e0c1a422e9b90a487fa78cfef15c0
Timestamp: 1759596895 Timestamp [UTC]: 2025-10-04 16:54:55 Age [y:d:h:m:s]: 01:041:22:47:59
Block: 1382718 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296279 RingCT/type: yes/0
Extra: 012a6e5a52e5d2bde1218373f4ff7bea46b91e0c1a422e9b90a487fa78cfef15c002110000000397baf922000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 040a56d19fb6c374e176e78692b32efc9c7fe43d01399ff470025a55471a692a 0.000600000000 1870853 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": 1382728, "vin": [ { "gen": { "height": 1382718 } } ], "vout": [ { "amount": 600000000, "target": { "key": "040a56d19fb6c374e176e78692b32efc9c7fe43d01399ff470025a55471a692a" } } ], "extra": [ 1, 42, 110, 90, 82, 229, 210, 189, 225, 33, 131, 115, 244, 255, 123, 234, 70, 185, 30, 12, 26, 66, 46, 155, 144, 164, 135, 250, 120, 207, 239, 21, 192, 2, 17, 0, 0, 0, 3, 151, 186, 249, 34, 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: