Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e559196ab6a19332d1d606dbd78e109e929459cafb859d091d6eb58c8754621

Tx prefix hash: 23e30f9ba8374a833602554be906af7432f6abad8f4439b0ed078862676296d3
Tx public key: 3b647ff2f531cee5a269d150763f87a4c40a9b828492a969b716c485f1625ab5
Timestamp: 1745839138 Timestamp [UTC]: 2025-04-28 11:18:58 Age [y:d:h:m:s]: 01:206:09:43:25
Block: 1271263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411672 RingCT/type: yes/0
Extra: 013b647ff2f531cee5a269d150763f87a4c40a9b828492a969b716c485f1625ab502110000000125a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 953f9c6974c4a810eefb32bd71d5e7ada59d4cd565acef806a903cdfea79ae7b 0.000600000000 1758520 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": 1271273, "vin": [ { "gen": { "height": 1271263 } } ], "vout": [ { "amount": 600000000, "target": { "key": "953f9c6974c4a810eefb32bd71d5e7ada59d4cd565acef806a903cdfea79ae7b" } } ], "extra": [ 1, 59, 100, 127, 242, 245, 49, 206, 229, 162, 105, 209, 80, 118, 63, 135, 164, 196, 10, 155, 130, 132, 146, 169, 105, 183, 22, 196, 133, 241, 98, 90, 181, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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: