Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e442b5b7e233bea45204c2a2e60de6c8b48b6af564467392fe236741ebb2c0e

Tx prefix hash: 35579f14acddfa5720c85584049813d18dd7d010178dc05772aa235e338032c9
Tx public key: f0692a3dbeb91e3fb414fceaccec877c780051d8df972cbda801efb504bb1889
Timestamp: 1771507844 Timestamp [UTC]: 2026-02-19 13:30:44 Age [y:d:h:m:s]: 00:273:00:29:51
Block: 1481227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200714 RingCT/type: yes/0
Extra: 01f0692a3dbeb91e3fb414fceaccec877c780051d8df972cbda801efb504bb1889021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fcbc7413f18ad65a8c2b21e36edc06c31ee64e18a2792bce006fa75a09f61a03 0.000600000000 1970603 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": 1481237, "vin": [ { "gen": { "height": 1481227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcbc7413f18ad65a8c2b21e36edc06c31ee64e18a2792bce006fa75a09f61a03" } } ], "extra": [ 1, 240, 105, 42, 61, 190, 185, 30, 63, 180, 20, 252, 234, 204, 236, 135, 124, 120, 0, 81, 216, 223, 151, 44, 189, 168, 1, 239, 181, 4, 187, 24, 137, 2, 17, 0, 0, 0, 4, 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: