Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 538dc802d72c6dca896240c2d644ae6bd3bd5e9e491dcdb94f7acee29023b568

Tx prefix hash: 2d1a09b10a7c9a95ad956116ee7899c83dfee22d0c420b4eeb37dc4af1fc78b9
Tx public key: 5e7eb7a3ffd2916d1cbba34b9d014b214de0d2b9cb8fdefc7b897e0843a51cf8
Timestamp: 1789029647 Timestamp [UTC]: 2026-09-10 08:40:47 Age [y:d:h:m:s]: 00:065:22:16:42
Block: 1632233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 46484 RingCT/type: yes/0
Extra: 015e7eb7a3ffd2916d1cbba34b9d014b214de0d2b9cb8fdefc7b897e0843a51cf8

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: df1043bc0bf4b941e4e566cfdacd4d42e6c90bfe1b20076c2341d54ab4e64f67 0.000600000000 2122253 of 15 <c8>

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": 1632243, "vin": [ { "gen": { "height": 1632233 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "df1043bc0bf4b941e4e566cfdacd4d42e6c90bfe1b20076c2341d54ab4e64f67", "view_tag": "c8" } } } ], "extra": [ 1, 94, 126, 183, 163, 255, 210, 145, 109, 28, 187, 163, 75, 157, 1, 75, 33, 77, 224, 210, 185, 203, 143, 222, 252, 123, 137, 126, 8, 67, 165, 28, 248 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: