Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22c143718e6574f33a65c70328620ebca8a4c40cbe4259e3eda469dbcc60c9e2

Tx prefix hash: 252aebc78f759a40ad688f1a1208dae08a226f4b43aee66307195ae91178eaa6
Tx public key: 804e7d070613b894eda47aeb863d4eec61994f3ecfa21700f45593bd5903794d
Timestamp: 1771459026 Timestamp [UTC]: 2026-02-18 23:57:06 Age [y:d:h:m:s]: 00:274:13:23:17
Block: 1480827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201893 RingCT/type: yes/0
Extra: 01804e7d070613b894eda47aeb863d4eec61994f3ecfa21700f45593bd5903794d021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6ffe59c1a50e60fd537671e2946589cd9f6c5bc5e36e5aebf0c2af2409900a09 0.000600000000 1970199 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": 1480837, "vin": [ { "gen": { "height": 1480827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ffe59c1a50e60fd537671e2946589cd9f6c5bc5e36e5aebf0c2af2409900a09" } } ], "extra": [ 1, 128, 78, 125, 7, 6, 19, 184, 148, 237, 164, 122, 235, 134, 61, 78, 236, 97, 153, 79, 62, 207, 162, 23, 0, 244, 85, 147, 189, 89, 3, 121, 77, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: