← previous blocknext block →recent activity
Analyzing
Block #89,664,771
12 transactions · 11 stateful · 2026-07-23 15:15:48 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,664,771 · 12 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
1w02w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea91b36f…dfd4
0x34b655…2a6f
4 touches
1 conflict
0x34ac5036…bedf
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x1ef3d54e…667a
0x34b655…2a6f
2 touches
0 conflicts
0x2d58a69f…6820
0x34b655…2a6f
2 touches
0 conflicts
0xd733f76d…16f5
0x34b655…2a6f
2 touches
0 conflicts
0x3f957e98…4a58
0x34b655…2a6f
2 touches
0 conflicts
0x3fa02211…d4f6
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 0xea91b36f83…37dfd4
Audit this contract →
← previous block·next block →recent activity