Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0effd94aea57f88d33c9c768cf8b26a94cf591290a46ef5b5ec4e47f0eeab65b

Tx prefix hash: 3237f4bd276b57027e682c1cbffcf341d98816e16af397eba01c8f632b9d9413
Tx public key: 668e56a616bb766c6436cd08ac7711bf722c58306ffee2404b895abae5f9781f
Timestamp: 1773707193 Timestamp [UTC]: 2026-03-17 00:26:33 Age [y:d:h:m:s]: 00:243:00:08:36
Block: 1499435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179072 RingCT/type: yes/0
Extra: 01668e56a616bb766c6436cd08ac7711bf722c58306ffee2404b895abae5f9781f021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ee2194aa17b32714578d8b4754bc6d3f4c35f64bf31f2b73d3dc45a3d80f8ce6 0.000600000000 1989093 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": 1499445, "vin": [ { "gen": { "height": 1499435 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee2194aa17b32714578d8b4754bc6d3f4c35f64bf31f2b73d3dc45a3d80f8ce6" } } ], "extra": [ 1, 102, 142, 86, 166, 22, 187, 118, 108, 100, 54, 205, 8, 172, 119, 17, 191, 114, 44, 88, 48, 111, 254, 226, 64, 75, 137, 90, 186, 229, 249, 120, 31, 2, 17, 0, 0, 0, 1, 228, 245, 25, 63, 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: