← previous blocknext block →recent activity
Analyzing
Block #88,075,599
18 transactions · 15 stateful · 2026-07-16 06:21:34 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,075,599 · 18 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
3w04w15w07w210w011w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5c56995…6d22
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4cc58517…ce14
0x34b655…2a6f
4 touches
1 conflict
0x5c16527f…628c
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0xa0a5bed4…1d15
0x34b655…2a6f
4 touches
1 conflict
0xa90dbfd2…06e0
0x34b655…2a6f
4 touches
1 conflict
0xb54c8ced…5b8c
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 0xd5c5699561…d46d22
Audit this contract →
← previous block·next block →recent activity