← previous blocknext block →recent activity
Analyzing
Block #95,782,921
17 transactions · 17 stateful · 2026-08-14 01:12:24 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,782,921 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w110w211w313w214w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x544dcd8f…f456
0x34b655…2a6f
8 touches
6 conflicts
0x91cdfdeb…7feb
0x34b655…2a6f
6 touches
3 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
6 touches
3 conflicts
0x628359b1…7263
0x34b655…2a6f
6 touches
3 conflicts
0x71c72ebc…dbbb
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7e95fe64…7024
0x851145…3f07
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity