← previous blocknext block →recent activity
Analyzing
Block #89,703,138
13 transactions · 12 stateful · 2026-07-23 18:30:03 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,703,138 · 13 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00842ba8…bdc6
0x34b655…2a6f
2 touches
0 conflicts
0x00c7c856…6e59
0x34b655…2a6f
2 touches
0 conflicts
0x08a39015…efa0
0x34b655…2a6f
2 touches
0 conflicts
0x2d55c77c…0618
0x34b655…2a6f
2 touches
0 conflicts
0x34413116…952e
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 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity