← previous blocknext block →recent activity
Analyzing
Block #88,139,043
23 transactions · 22 stateful · 2026-07-16 13:26:00 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,139,043 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w010w111w212w113w214w315w417w518w621w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x6e27bdfb…108a
0x34b655…2a6f
8 touches
6 conflicts
0xe8810a49…939a
0x34b655…2a6f
6 touches
3 conflicts
0x145b9bbf…e50f
0x34b655…2a6f
6 touches
3 conflicts
0x901f4dfc…1ba4
0x34b655…2a6f
6 touches
3 conflicts
0xa83fcf1a…0854
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity