← previous blocknext block →recent activity
Analyzing
Block #89,882,765
11 transactions · 9 stateful · 2026-07-24 09:36:10 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,882,765 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9d6d235c…3d64
0x34b655…2a6f
4 touches
1 conflict
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0x1122aa18…abac
0x34b655…2a6f
2 touches
0 conflicts
0x187bb168…d783
0x34b655…2a6f
2 touches
0 conflicts
0x3accf018…2e8b
0x34b655…2a6f
2 touches
0 conflicts
0x4ccb5334…7c73
0x34b655…2a6f
2 touches
0 conflicts
0x4e7d4671…71c1
0x34b655…2a6f
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
1 conflict on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity