← previous blocknext block →recent activity
Analyzing
Block #88,138,399
14 transactions · 13 stateful · 2026-07-16 13:21:41 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,138,399 · 14 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
2w03w15w06w17w29w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6dd5be0…26d6
0x34b655…2a6f
6 touches
3 conflicts
0xf788c790…e66f
0x34b655…2a6f
4 touches
1 conflict
0x606bc50d…4c10
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0x9465204c…bf37
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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 0xb6dd5be053…0526d6
Audit this contract →
← previous block·next block →recent activity