Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3492319e6831de2deca5a3e77500a12940e8cb4921c09936b88870ebaee2d0f2

Tx prefix hash: 993f80637519751549cec40938188e6df291a930bee13a78e3cd0bff735f6eeb
Tx public key: 9ee5758b2d2e0c59dcf51e0240b91521f0d07c09531499cb6407f60b948eee2b
Timestamp: 1774933065 Timestamp [UTC]: 2026-03-31 04:57:45 Age [y:d:h:m:s]: 00:228:19:50:14
Block: 1509563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168954 RingCT/type: yes/0
Extra: 019ee5758b2d2e0c59dcf51e0240b91521f0d07c09531499cb6407f60b948eee2b021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 902a54d70ed60ad37ff653edaf4ad3f160ce078f9de9f42fb745724a9fb9a377 0.000600000000 1999339 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": 1509573, "vin": [ { "gen": { "height": 1509563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "902a54d70ed60ad37ff653edaf4ad3f160ce078f9de9f42fb745724a9fb9a377" } } ], "extra": [ 1, 158, 229, 117, 139, 45, 46, 12, 89, 220, 245, 30, 2, 64, 185, 21, 33, 240, 208, 124, 9, 83, 20, 153, 203, 100, 7, 246, 11, 148, 142, 238, 43, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 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: