← previous blocknext block →recent activity
Analyzing
Block #96,622,771
20 transactions · 18 stateful · 2026-08-16 23:37:24 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,622,771 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w112w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x02991b41…19e6
0x34b655…2a6f
4 touches
1 conflict
0x0b05d77e…6f90
0x34b655…2a6f
4 touches
1 conflict
0xf5f815e7…c83e
0x34b655…2a6f
4 touches
1 conflict
0x47b5e356…2641
0x34b655…2a6f
4 touches
1 conflict
0xcea40325…6b39
0x34b655…2a6f
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
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