← previous blocknext block →recent activity
Analyzing
Block #88,138,831
18 transactions · 18 stateful · 2026-07-16 13:24:35 UTC
Parallelism
89/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,138,831 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w18w09w110w013w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6e6f436…ddc0
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x28e32856…45f6
0x34b655…2a6f
4 touches
1 conflict
0x3823262a…1944
0xa6afd3…d132
3 touches
1 conflict
0xd836dfaa…2853
0x065c9d…c394
3 touches
1 conflict
0xba5743c7…21c4
0x1b6862…e19c
2 touches
0 conflicts
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 0xe6e6f4364f…80ddc0
Audit this contract →
← previous block·next block →recent activity