Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e836dd0309b60bba8ea0a346abaeb604d0371663fa66b0889c5b7843683ad8d

Tx prefix hash: 5c53d32309c60ea5eb88dadc1efe157a7284c56f243506570c2bf129997d6f7a
Tx public key: a00d797977ea40ed790173d940b4e3e997f1fa086081ecb19905f31f239d60db
Timestamp: 1746964460 Timestamp [UTC]: 2025-05-11 11:54:20 Age [y:d:h:m:s]: 01:190:13:24:54
Block: 1280577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400208 RingCT/type: yes/0
Extra: 01a00d797977ea40ed790173d940b4e3e997f1fa086081ecb19905f31f239d60db02110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a0ba00b8a8ade77f6bc890f9727a157f47e1bb9cb8a67400b99a11329b7bfb24 0.000600000000 1767966 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": 1280587, "vin": [ { "gen": { "height": 1280577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0ba00b8a8ade77f6bc890f9727a157f47e1bb9cb8a67400b99a11329b7bfb24" } } ], "extra": [ 1, 160, 13, 121, 121, 119, 234, 64, 237, 121, 1, 115, 217, 64, 180, 227, 233, 151, 241, 250, 8, 96, 129, 236, 177, 153, 5, 243, 31, 35, 157, 96, 219, 2, 17, 0, 0, 0, 10, 159, 159, 230, 140, 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: