Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a542b2643e4e5c3882f30a637dfbe9a5fd64ec02f1927b1a49cc4ab0f8563ea3

Tx prefix hash: bd3fc20c02eee7aa643c685071f80e955a98af45ae70a3d51ab5ede0419c38d3
Tx public key: 4706780d1ca88aded2c5a0686e9f8e038bdf2107f47f7edd31782d365ccf02a5
Timestamp: 1748018064 Timestamp [UTC]: 2025-05-23 16:34:24 Age [y:d:h:m:s]: 01:178:02:28:09
Block: 1289306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391270 RingCT/type: yes/0
Extra: 014706780d1ca88aded2c5a0686e9f8e038bdf2107f47f7edd31782d365ccf02a50211000000019f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: be82ca3feefd50388986977edf572e46439e849d815c044f61764edbaefb1e7b 0.000600000000 1776773 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": 1289316, "vin": [ { "gen": { "height": 1289306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be82ca3feefd50388986977edf572e46439e849d815c044f61764edbaefb1e7b" } } ], "extra": [ 1, 71, 6, 120, 13, 28, 168, 138, 222, 210, 197, 160, 104, 110, 159, 142, 3, 139, 223, 33, 7, 244, 127, 126, 221, 49, 120, 45, 54, 92, 207, 2, 165, 2, 17, 0, 0, 0, 1, 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: