Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d96f17b65ffeb5ac92272cc12fdb7584c66ea213054244260edaf63dc4dbcb1

Tx prefix hash: 5fdc693b94af4a6c4abbb3b1d9f34340ca7ed43ba9f3fea39a4a9e1edb96a384
Tx public key: 63569daa5915134684267b1d22b13e4cfb9f3425e4837db5bc0f25ed1ba5bc49
Timestamp: 1772830416 Timestamp [UTC]: 2026-03-06 20:53:36 Age [y:d:h:m:s]: 00:256:07:27:59
Block: 1492185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188698 RingCT/type: yes/0
Extra: 0163569daa5915134684267b1d22b13e4cfb9f3425e4837db5bc0f25ed1ba5bc49021100000007f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 768877a30494490fef99433780855e0dcc301658d6453b09195048445a0c9fd1 0.000600000000 1981723 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": 1492195, "vin": [ { "gen": { "height": 1492185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "768877a30494490fef99433780855e0dcc301658d6453b09195048445a0c9fd1" } } ], "extra": [ 1, 99, 86, 157, 170, 89, 21, 19, 70, 132, 38, 123, 29, 34, 177, 62, 76, 251, 159, 52, 37, 228, 131, 125, 181, 188, 15, 37, 237, 27, 165, 188, 73, 2, 17, 0, 0, 0, 7, 241, 136, 200, 168, 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: