Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68c7dfcea9fab82937361c0a3cf4a16c2d3da0c107164559b0c751bf58dc3232

Tx prefix hash: 3acdd3d251fd9c85ca406408e9b440520633e62c343cfb77b7a0dc8473ba6771
Tx public key: 54fbf0a817ac4e4c8af8e96c74271acff38f24a099e3c64e883aed572894f6b6
Timestamp: 1747691760 Timestamp [UTC]: 2025-05-19 21:56:00 Age [y:d:h:m:s]: 01:181:10:51:28
Block: 1286592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393676 RingCT/type: yes/0
Extra: 0154fbf0a817ac4e4c8af8e96c74271acff38f24a099e3c64e883aed572894f6b60211000000069f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 49394ada8d76d0d77fdca5b14fc382eb7f85cad590944b46f3e1b14a9a579b2c 0.000600000000 1774059 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": 1286602, "vin": [ { "gen": { "height": 1286592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49394ada8d76d0d77fdca5b14fc382eb7f85cad590944b46f3e1b14a9a579b2c" } } ], "extra": [ 1, 84, 251, 240, 168, 23, 172, 78, 76, 138, 248, 233, 108, 116, 39, 26, 207, 243, 143, 36, 160, 153, 227, 198, 78, 136, 58, 237, 87, 40, 148, 246, 182, 2, 17, 0, 0, 0, 6, 159, 159, 230, 140, 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: