Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64a00b33b89601eefaa0c0cc2a82b1384452cf4916c9f01ba123383adefda7c4

Tx prefix hash: 52838de979be8025dd51b435cb4accc7c4d6b451f72a342d0a87fe085e978115
Tx public key: d15b44fd67a654370a84352dd6e92643369b266504e9f654f17958c59796c3f3
Timestamp: 1752214352 Timestamp [UTC]: 2025-07-11 06:12:32 Age [y:d:h:m:s]: 01:133:06:57:31
Block: 1323099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360327 RingCT/type: yes/0
Extra: 01d15b44fd67a654370a84352dd6e92643369b266504e9f654f17958c59796c3f3021100000002d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1af68c33112ed5d6ee2ed30cf87a32545edb54815f2358898dc539fb004e6f70 0.000600000000 1810834 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": 1323109, "vin": [ { "gen": { "height": 1323099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1af68c33112ed5d6ee2ed30cf87a32545edb54815f2358898dc539fb004e6f70" } } ], "extra": [ 1, 209, 91, 68, 253, 103, 166, 84, 55, 10, 132, 53, 45, 214, 233, 38, 67, 54, 155, 38, 101, 4, 233, 246, 84, 241, 121, 88, 197, 151, 150, 195, 243, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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: