← previous blocknext block →recent activity
Analyzing
Block #88,138,813
17 transactions · 13 stateful · 2026-07-16 13:24:27 UTC
Parallelism
82/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,138,813 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w110w112w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28e32856…45f6
0x34b655…2a6f
6 touches
3 conflicts
0xd2052f35…5428
0x851145…3f07
4 touches
1 conflict
0xbe2f3517…dfb0
0x34b655…2a6f
4 touches
1 conflict
0xbe2f3517…dfb1
0x34b655…2a6f
4 touches
1 conflict
0xe1caddba…a708
0x34b655…2a6f
4 touches
1 conflict
0xe3f11ed8…a8a6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x70da80f3…a8f7
0x851145…3f07
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 0x28e32856a1…7845f6
Audit this contract →
← previous block·next block →recent activity