← previous blocknext block →recent activity
Analyzing
Block #89,863,124
20 transactions · 19 stateful · 2026-07-24 07:57:23 UTC
Parallelism
80/100
Blocked
21%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,863,124 · 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
5w09w111w012w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc516fef7…841c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x2d12b1f8…f87e
0x34b655…2a6f
6 touches
3 conflicts
0xecf774ff…e56d
0x34b655…2a6f
6 touches
3 conflicts
0x326a02b5…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x61e01cd0…b73e
0x34b655…2a6f
4 touches
1 conflict
0x61e01cd0…b73f
0x34b655…2a6f
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 0xc516fef749…a5841c
Audit this contract →
← previous block·next block →recent activity