← previous blocknext block →recent activity
Analyzing
Block #88,140,092
26 transactions · 21 stateful · 2026-07-16 13:33:00 UTC
Parallelism
69/100
Blocked
43%
Avg conflicts / tx
0.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #88,140,092 · 26 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
3w04w110w011w112w213w314w416w517w221w625w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
6 touches
3 conflicts
0x26763d4e…651f
0x34b655…2a6f
4 touches
1 conflict
0x2857a1ac…d729
0x34b655…2a6f
4 touches
1 conflict
0x3149127f…19a9
0x34b655…2a6f
4 touches
1 conflict
0x32e5ca7f…d8e9
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d8
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
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
10 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity