Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f7c6c8fbe749b1ea364d8b282d80f260121d4b49b044b8a26f5ce6382a3ad8

Tx prefix hash: a2981a7a0ba9b9a3ed6ac354f44ddf0fec8cc38028910eb08a39d1df75f27c7f
Tx public key: ac29a31b765eb9041350dbdf7a2c3da8deb266d99364b8b3eb460ad21a8ee7d1
Timestamp: 1772492148 Timestamp [UTC]: 2026-03-02 22:55:48 Age [y:d:h:m:s]: 00:255:09:04:57
Block: 1489375 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187874 RingCT/type: yes/0
Extra: 01ac29a31b765eb9041350dbdf7a2c3da8deb266d99364b8b3eb460ad21a8ee7d1021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a023df718af7abc44496eeea9cc293c6beb0c9249b506dde57778e4e4d4ca7d 0.000600000000 1978865 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": 1489385, "vin": [ { "gen": { "height": 1489375 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a023df718af7abc44496eeea9cc293c6beb0c9249b506dde57778e4e4d4ca7d" } } ], "extra": [ 1, 172, 41, 163, 27, 118, 94, 185, 4, 19, 80, 219, 223, 122, 44, 61, 168, 222, 178, 102, 217, 147, 100, 184, 179, 235, 70, 10, 210, 26, 142, 231, 209, 2, 17, 0, 0, 0, 3, 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: