Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba0222070e07233c3d7dc959d3bc40cf2e9d3bb7e17d23d207dad9fb568e3075

Tx prefix hash: 8c0082628709877424666bcf37e0a18b78564be79b54a1ff843d5a71159e3323
Tx public key: eb207a14ea33c193a7bddc7291a75312699d474557b38b0cda175db658b068d5
Timestamp: 1745607925 Timestamp [UTC]: 2025-04-25 19:05:25 Age [y:d:h:m:s]: 01:206:14:05:58
Block: 1269346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411682 RingCT/type: yes/0
Extra: 01eb207a14ea33c193a7bddc7291a75312699d474557b38b0cda175db658b068d50211000000018368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b38de4e38b488be580e830063948fe75e5c8f8e69fed26cad08ac3fd107797b1 0.000600000000 1756581 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": 1269356, "vin": [ { "gen": { "height": 1269346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b38de4e38b488be580e830063948fe75e5c8f8e69fed26cad08ac3fd107797b1" } } ], "extra": [ 1, 235, 32, 122, 20, 234, 51, 193, 147, 167, 189, 220, 114, 145, 167, 83, 18, 105, 157, 71, 69, 87, 179, 139, 12, 218, 23, 93, 182, 88, 176, 104, 213, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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: