← previous blocknext block →recent activity
Analyzing
Block #88,358,972
19 transactions · 17 stateful · 2026-07-17 13:57:57 UTC
Parallelism
58/100
Blocked
65%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #88,358,972 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w410w511w617w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x1e166a45…98a7
0x34b655…2a6f
6 touches
3 conflicts
0x8e4fdba3…18f1
0x34b655…2a6f
6 touches
3 conflicts
0x35a9f06c…7689
0x34b655…2a6f
6 touches
3 conflicts
0xdb258a42…9814
0xd32edf…ff58
5 touches
3 conflicts
0x93afca4c…b47a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity