← previous blocknext block →recent activity
Analyzing
Block #89,784,471
10 transactions · 8 stateful · 2026-07-24 01:20:44 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,784,471 · 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
3w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad5139c1…38c6
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x2f233eb3…6f16
0x34b655…2a6f
2 touches
0 conflicts
0x3e3f27ce…580c
0x34b655…2a6f
2 touches
0 conflicts
0x52aa1020…c85c
0x34b655…2a6f
2 touches
0 conflicts
0x5d3bdba3…669e
0x34b655…2a6f
2 touches
0 conflicts
0x69c491e3…98d9
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 0xad5139c18e…df38c6
Audit this contract →
← previous block·next block →recent activity