Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22ba0c598c79ca94c04c7a57039e5dec370da5d49c816fc18e31cc807a874aa0

Tx prefix hash: b1009287e1461071d00c010046f4a32db5e74a95cbe90d49cd60073400f0facd
Tx public key: 85aef58176ef4a47b9fba7814c331261ef6d121bfe6e9892d7536b96fcd7c311
Timestamp: 1717692136 Timestamp [UTC]: 2024-06-06 16:42:16 Age [y:d:h:m:s]: 01:343:22:03:33
Block: 1038422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496737 RingCT/type: yes/0
Extra: 0185aef58176ef4a47b9fba7814c331261ef6d121bfe6e9892d7536b96fcd7c31102110000000559dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6032b8aafe36ef550e5bfd0f952a94f32da65e5bb90ba468892ce79dae6a6889 0.000600000000 1506983 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": 1038432, "vin": [ { "gen": { "height": 1038422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6032b8aafe36ef550e5bfd0f952a94f32da65e5bb90ba468892ce79dae6a6889" } } ], "extra": [ 1, 133, 174, 245, 129, 118, 239, 74, 71, 185, 251, 167, 129, 76, 51, 18, 97, 239, 109, 18, 27, 254, 110, 152, 146, 215, 83, 107, 150, 252, 215, 195, 17, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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: