← previous blocknext block →recent activity
Analyzing
Block #89,566,935
11 transactions · 9 stateful · 2026-07-23 04:35:18 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,566,935 · 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
5w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a39a2a4…857b
0x34b655…2a6f
4 touches
1 conflict
0xbbad01bd…c7e4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x947bb79d…6458
0x34b655…2a6f
4 touches
1 conflict
0xad2b505f…1897
0x34b655…2a6f
4 touches
1 conflict
0x33c2d4e5…8636
0x34b655…2a6f
2 touches
0 conflicts
0x39c5e2b9…b634
0x34b655…2a6f
2 touches
0 conflicts
0x72470f81…c402
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 0x4a39a2a411…a6857b
Audit this contract →
← previous block·next block →recent activity