Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 018f1fe061102fbde6add188ca7186a381d926cbb34d495cbefec40524ee8112

Tx prefix hash: 6eda973b5599cc15fe95c04b4a5b8acfb2812b0bad2293d66b2c1517caab5c2f
Tx public key: 68be8edc4546f9a05087b2d3fe978047d4bb2da446a4b1e5be1e488264198425
Timestamp: 1771499622 Timestamp [UTC]: 2026-02-19 11:13:42 Age [y:d:h:m:s]: 00:273:09:54:27
Block: 1481163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200994 RingCT/type: yes/0
Extra: 0168be8edc4546f9a05087b2d3fe978047d4bb2da446a4b1e5be1e488264198425021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ea5fee16cce1c8c2c5a6756ecc027d4ad67a4d8bb1394826b6229bfcc8259f7b 0.000600000000 1970539 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": 1481173, "vin": [ { "gen": { "height": 1481163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea5fee16cce1c8c2c5a6756ecc027d4ad67a4d8bb1394826b6229bfcc8259f7b" } } ], "extra": [ 1, 104, 190, 142, 220, 69, 70, 249, 160, 80, 135, 178, 211, 254, 151, 128, 71, 212, 187, 45, 164, 70, 164, 177, 229, 190, 30, 72, 130, 100, 25, 132, 37, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: