← previous blocknext block →recent activity
Analyzing
Block #88,193,508
20 transactions · 19 stateful · 2026-07-16 19:31:10 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,193,508 · 20 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
1w04w05w17w28w19w310w011w112w216w317w418w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x3eb4c216…f6f1
0x0a2fbf…29b1
6 touches
3 conflicts
0x3eb4c216…f6f2
0x0a2fbf…29b1
6 touches
3 conflicts
0xa09c1010…5409
0x0a2fbf…29b1
6 touches
3 conflicts
0xa09c1010…540a
0x0a2fbf…29b1
6 touches
3 conflicts
0xa09c1010…540d
0x0a2fbf…29b1
6 touches
3 conflicts
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0xc824469a…6425
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
6 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity