Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 388c3f4e26223c25b13b9f77eaf8084d2d9965303536bec9367f5b820e71d12e

Tx prefix hash: f1545559d03a80e2a684d0e972c45c84ad9a7ab8f0b6aa39942ad4b87495d76e
Tx public key: 3294e006f8d3a5b99b1cfde7b247721b03def64e2623d1f1f67a4c6bfc279209
Timestamp: 1776828314 Timestamp [UTC]: 2026-04-22 03:25:14 Age [y:d:h:m:s]: 00:023:19:43:56
Block: 1517526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 17181 RingCT/type: yes/0
Extra: 013294e006f8d3a5b99b1cfde7b247721b03def64e2623d1f1f67a4c6bfc279209

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 08b1a1e6651985b441a1308d8cee701d3a5ffc304fa6be3df53be3a0f9f3eba8 0.000600000000 2007374 of 15 <2e>

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": 1517536, "vin": [ { "gen": { "height": 1517526 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "08b1a1e6651985b441a1308d8cee701d3a5ffc304fa6be3df53be3a0f9f3eba8", "view_tag": "2e" } } } ], "extra": [ 1, 50, 148, 224, 6, 248, 211, 165, 185, 155, 28, 253, 231, 178, 71, 114, 27, 3, 222, 246, 78, 38, 35, 209, 241, 246, 122, 76, 107, 252, 39, 146, 9 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: