← previous blocknext block →recent activity
Analyzing
Block #88,356,094
34 transactions · 27 stateful · 2026-07-17 13:38:33 UTC
Parallelism
82/100
Blocked
52%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,356,094 · 34 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
3w04w110w011w112w213w315w416w520w121w222w224w226w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x006ee1d9…5485
0xa6afd3…d132
8 touches
6 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0xbcdee322…f454
0xa6afd3…d132
6 touches
3 conflicts
0x3413a430…234a
0x34b655…2a6f
4 touches
1 conflict
0x4640a06d…5986
0x34b655…2a6f
4 touches
1 conflict
0x655c1a0c…c2c9
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
15 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity