Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 481b361c46ca01b6584f77a59d73bd87f505a8947c4b038da2fa7e41df7d78d5

Tx prefix hash: d2695b5179169625ad88898317582f4112e40e955404b0d82d772b4652e3998f
Tx public key: 21896d66a2c397400d051e37a59177349e521fc4ccde351c6b3ffd69db98c5bd
Timestamp: 1772813583 Timestamp [UTC]: 2026-03-06 16:13:03 Age [y:d:h:m:s]: 00:255:16:27:22
Block: 1492042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188224 RingCT/type: yes/0
Extra: 0121896d66a2c397400d051e37a59177349e521fc4ccde351c6b3ffd69db98c5bd021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 05c673ab0e44bb8664bc4dea95ffddd47a57ab9ddc1cc51b5dfe486e3bba9e32 0.000600000000 1981580 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": 1492052, "vin": [ { "gen": { "height": 1492042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05c673ab0e44bb8664bc4dea95ffddd47a57ab9ddc1cc51b5dfe486e3bba9e32" } } ], "extra": [ 1, 33, 137, 109, 102, 162, 195, 151, 64, 13, 5, 30, 55, 165, 145, 119, 52, 158, 82, 31, 196, 204, 222, 53, 28, 107, 63, 253, 105, 219, 152, 197, 189, 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: