Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4fe6b4e5f12632448fb71d506451a8f71f7b2b3fa4fd0d7c8956fe976b4f1df

Tx prefix hash: c16240f3a7e5ef3e01f8bd1f30af20ec23b96c5d3af760105b600a44dedfc6a4
Tx public key: 343aaa79c1deaf6341c45842f49cc1eba45e87484b9f124166c4d0193ad5dea1
Timestamp: 1737607582 Timestamp [UTC]: 2025-01-23 04:46:22 Age [y:d:h:m:s]: 01:296:16:44:03
Block: 1203340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475833 RingCT/type: yes/0
Extra: 01343aaa79c1deaf6341c45842f49cc1eba45e87484b9f124166c4d0193ad5dea102110000000c007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0de7dc1df9da66f54d2375dafcaf12d27df80221e7573878a331ed62bfdf4f1e 0.000600000000 1690017 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": 1203350, "vin": [ { "gen": { "height": 1203340 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0de7dc1df9da66f54d2375dafcaf12d27df80221e7573878a331ed62bfdf4f1e" } } ], "extra": [ 1, 52, 58, 170, 121, 193, 222, 175, 99, 65, 196, 88, 66, 244, 156, 193, 235, 164, 94, 135, 72, 75, 159, 18, 65, 102, 196, 208, 25, 58, 213, 222, 161, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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: