← previous blocknext block →recent activity
Analyzing
Block #88,138,914
23 transactions · 22 stateful · 2026-07-16 13:25:08 UTC
Parallelism
78/100
Blocked
36%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,138,914 · 23 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
1w02w03w14w15w06w18w210w211w012w017w118w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf0b45960…2a3c
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x9465204c…bf37
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x108a530b…e797
0xd32edf…ff58
5 touches
3 conflicts
0x14d1bf0e…e09e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0xf0b45960e7…c92a3c
Audit this contract →
← previous block·next block →recent activity