← previous blocknext block →recent activity
Analyzing
Block #89,880,826
10 transactions · 9 stateful · 2026-07-24 09:26:25 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,880,826 · 10 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
3w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2006bbe4…04dc
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x71a3fd70…4a5b
0x34b655…2a6f
4 touches
1 conflict
0xba2bbf3f…98c0
0x34b655…2a6f
4 touches
1 conflict
0xcc3678e9…76f7
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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 0x2006bbe4bf…c004dc
Audit this contract →
← previous block·next block →recent activity