← previous blocknext block →recent activity
Analyzing
Block #88,193,878
12 transactions · 11 stateful · 2026-07-16 19:33:38 UTC
Parallelism
58/100
Blocked
55%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,193,878 · 12 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
2w04w15w26w37w48w39w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x3661f59a…874a
0x34b655…2a6f
6 touches
3 conflicts
0x200b13f5…2b4a
0x34b655…2a6f
4 touches
1 conflict
0x23b931c8…b581
0x34b655…2a6f
4 touches
1 conflict
0x2bad40ae…0523
0x34b655…2a6f
4 touches
1 conflict
0x3270d9f8…099a
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity