← previous blocknext block →recent activity
Analyzing
Block #88,160,131
20 transactions · 19 stateful · 2026-07-16 15:47:15 UTC
Parallelism
70/100
Blocked
42%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,160,131 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w09w210w111w212w314w118w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25ff7717…d4af
0x34b655…2a6f
10 touches
10 conflicts
0xe71412f7…a9ff
0xd32edf…ff58
5 touches
3 conflicts
0x9b1395e7…7654
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x029457db…3cd5
0x34b655…2a6f
4 touches
1 conflict
0xac3f143c…7638
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001e
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
10 conflicts on slot 0x25ff77178c…2ad4af
Audit this contract →
← previous block·next block →recent activity