← previous blocknext block →recent activity
Analyzing
Block #89,278,963
19 transactions · 16 stateful · 2026-07-21 20:30:58 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,278,963 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w110w211w312w317w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcadf8b62…6261
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x62ef187f…3b2d
0x34b655…2a6f
4 touches
1 conflict
0x808b1b9c…3da2
0x34b655…2a6f
4 touches
1 conflict
0x8d6062bd…88e0
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa4ca05f8…706c
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
6 conflicts on slot 0xcadf8b62e9…736261
Audit this contract →
← previous block·next block →recent activity