Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 990d1fd82cef7df0551f4cb65edf1c340f76261df50b81c45e76e5f9c504170b

Tx prefix hash: d57bfbe3adfa707b1be1a45e01fb75f72aa2ae974fc5841be3bf69d089aa777a
Tx public key: 361363dc9d308bb86503aeadf4cf13879df9356ba5e2b72821a2b92a3836bd95
Timestamp: 1759073380 Timestamp [UTC]: 2025-09-28 15:29:40 Age [y:d:h:m:s]: 01:047:16:11:57
Block: 1378376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300366 RingCT/type: yes/0
Extra: 01361363dc9d308bb86503aeadf4cf13879df9356ba5e2b72821a2b92a3836bd95021100000006a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f5b01c0373f808e8eb7c94ae875bc1b2d6a58204f5d9bbfdc1b9995448f48b8 0.000600000000 1866471 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": 1378386, "vin": [ { "gen": { "height": 1378376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f5b01c0373f808e8eb7c94ae875bc1b2d6a58204f5d9bbfdc1b9995448f48b8" } } ], "extra": [ 1, 54, 19, 99, 220, 157, 48, 139, 184, 101, 3, 174, 173, 244, 207, 19, 135, 157, 249, 53, 107, 165, 226, 183, 40, 33, 162, 185, 42, 56, 54, 189, 149, 2, 17, 0, 0, 0, 6, 165, 220, 205, 121, 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: