Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b245d2a749a13c47025ab92c5d2bacdb3673c301eb59a801ac2918bf04f048f

Tx prefix hash: 6c5811cf707e6afdd17fc6b5415386c5671205ddcf6562f0cc84b06c324981a8
Tx public key: a8398b399ac36116992ea30a3b348b4b1ab0e4958612c70fa228e25e0515dac8
Timestamp: 1772934034 Timestamp [UTC]: 2026-03-08 01:40:34 Age [y:d:h:m:s]: 00:258:19:59:24
Block: 1493044 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190450 RingCT/type: yes/0
Extra: 01a8398b399ac36116992ea30a3b348b4b1ab0e4958612c70fa228e25e0515dac8021100000008f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9676822e56df5e514c3dc78e2c8d6e697eed5e0d9362c165501029bdd397a8b8 0.000600000000 1982598 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": 1493054, "vin": [ { "gen": { "height": 1493044 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9676822e56df5e514c3dc78e2c8d6e697eed5e0d9362c165501029bdd397a8b8" } } ], "extra": [ 1, 168, 57, 139, 57, 154, 195, 97, 22, 153, 46, 163, 10, 59, 52, 139, 75, 26, 176, 228, 149, 134, 18, 199, 15, 162, 40, 226, 94, 5, 21, 218, 200, 2, 17, 0, 0, 0, 8, 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: