Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3be5e15309b215887934dcbcf4ccf8a4972828da5474bfb9c7c10ddf51e5817c

Tx prefix hash: 26e0196b3f9bbb01937d8958246801146caae62fc3f4bbce29496e1472c6dd5f
Tx public key: c2dbfadbdaf49bf997294a908ceeac73be56ee64307b919f278cf38903bda15e
Timestamp: 1705225354 Timestamp [UTC]: 2024-01-14 09:42:34 Age [y:d:h:m:s]: 02:312:05:57:20
Block: 935053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 748441 RingCT/type: yes/0
Extra: 01c2dbfadbdaf49bf997294a908ceeac73be56ee64307b919f278cf38903bda15e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 715fc751bb8f3a9e243591c3e3be6411f9bfda934a702fb3747ae2e366aee1c0 0.000600000000 1393069 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": 935063, "vin": [ { "gen": { "height": 935053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "715fc751bb8f3a9e243591c3e3be6411f9bfda934a702fb3747ae2e366aee1c0" } } ], "extra": [ 1, 194, 219, 250, 219, 218, 244, 155, 249, 151, 41, 74, 144, 140, 238, 172, 115, 190, 86, 238, 100, 48, 123, 145, 159, 39, 140, 243, 137, 3, 189, 161, 94, 2, 17, 0, 0, 0, 2, 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: