← previous blocknext block →recent activity
Analyzing
Block #89,540,600
10 transactions · 10 stateful · 2026-07-23 01:39:20 UTC
Parallelism
70/100
Blocked
30%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,540,600 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x051aa260…b0a4
0x34b655…2a6f
4 touches
1 conflict
0x10cab052…8d64
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
4 touches
1 conflict
0x5f394770…ac95
0x34b655…2a6f
4 touches
1 conflict
0x6df97be9…fcaf
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
1 conflict on slot 0x051aa26053…b0b0a4
Audit this contract →
← previous block·next block →recent activity