Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7b285036266ab0d5169eeeaf468e2a9f66e53a6e69f8cd8dcc4c1f9c268fc10

Tx prefix hash: eda63616cebc3d1c3a842feda9908724565a960364d874b3f6e824f002647816
Tx public key: bcc0100253c32a40dc05f8bf1cbd1ded9b0abcc8135961627680a679a68a9744
Timestamp: 1774210828 Timestamp [UTC]: 2026-03-22 20:20:28 Age [y:d:h:m:s]: 00:244:12:31:22
Block: 1503575 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179919 RingCT/type: yes/0
Extra: 01bcc0100253c32a40dc05f8bf1cbd1ded9b0abcc8135961627680a679a68a9744021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 88080830706450649fdf894b504477b2b77db8c878d3b425cd042b476323cd26 0.000600000000 1993287 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": 1503585, "vin": [ { "gen": { "height": 1503575 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88080830706450649fdf894b504477b2b77db8c878d3b425cd042b476323cd26" } } ], "extra": [ 1, 188, 192, 16, 2, 83, 195, 42, 64, 220, 5, 248, 191, 28, 189, 29, 237, 155, 10, 188, 200, 19, 89, 97, 98, 118, 128, 166, 121, 166, 138, 151, 68, 2, 17, 0, 0, 0, 4, 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: