Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c070aeeb70c9f06f1eb3e455ce6002eba85708d620ad8b902985b86e19c0e80a

Tx prefix hash: db43c92dadd1f48bd3046bceddeeee0e368588e212ac429a3f6a6c33cc6fe1f0
Tx public key: 576cf819734dd0d4338fe9d8f05e785b11f610d9793538cc3bf5896dc8c971f8
Timestamp: 1750009181 Timestamp [UTC]: 2025-06-15 17:39:41 Age [y:d:h:m:s]: 01:065:11:18:49
Block: 1305692 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311579 RingCT/type: yes/0
Extra: 01576cf819734dd0d4338fe9d8f05e785b11f610d9793538cc3bf5896dc8c971f802110000000201491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fa042937094e03492416a71299f3bf2370b8ed82fca82b63421de738e12d827a 0.000600000000 1793293 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": 1305702, "vin": [ { "gen": { "height": 1305692 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa042937094e03492416a71299f3bf2370b8ed82fca82b63421de738e12d827a" } } ], "extra": [ 1, 87, 108, 248, 25, 115, 77, 208, 212, 51, 143, 233, 216, 240, 94, 120, 91, 17, 246, 16, 217, 121, 53, 56, 204, 59, 245, 137, 109, 200, 201, 113, 248, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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: