← previous blocknext block →recent activity
Analyzing
Block #89,700,861
18 transactions · 17 stateful · 2026-07-23 18:18:36 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #89,700,861 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w17w08w19w210w011w212w315w417w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3586d447…a796
0x34b655…2a6f
6 touches
3 conflicts
0x4b8f0c69…87d3
0x34b655…2a6f
6 touches
3 conflicts
0x81561f70…fefd
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x91f687f3…aca8
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9a6bc012…7495
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
3 conflicts on slot 0x3586d44724…2da796
Audit this contract →
← previous block·next block →recent activity