Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1adf23b30eb81b892cdded32d64756157525b2540942e81e893945b821b8745

Tx prefix hash: 75feb92911d59a39cc03fde4ec5ba400b10275b1a6d572f600e1880b042da1cc
Tx public key: 969ce413d3e508d040240d39d96ae41b02697f265e1ca0b8450ff7dbbd09a0d4
Timestamp: 1742390182 Timestamp [UTC]: 2025-03-19 13:16:22 Age [y:d:h:m:s]: 01:240:13:26:34
Block: 1242729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435851 RingCT/type: yes/0
Extra: 01969ce413d3e508d040240d39d96ae41b02697f265e1ca0b8450ff7dbbd09a0d40211000000041db82ba9000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a4123ff9dd007b05842b902abaacb9dc4ae1ec75454d315399c2d564230851eb 0.000600000000 1729704 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": 1242739, "vin": [ { "gen": { "height": 1242729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4123ff9dd007b05842b902abaacb9dc4ae1ec75454d315399c2d564230851eb" } } ], "extra": [ 1, 150, 156, 228, 19, 211, 229, 8, 208, 64, 36, 13, 57, 217, 106, 228, 27, 2, 105, 127, 38, 94, 28, 160, 184, 69, 15, 247, 219, 189, 9, 160, 212, 2, 17, 0, 0, 0, 4, 29, 184, 43, 169, 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: