← previous blocknext block →recent activity
Analyzing
Block #88,039,574
17 transactions · 16 stateful · 2026-07-16 02:20:39 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,039,574 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w09w110w311w114w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf78ee7f…e7fd
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x2a628ea8…5918
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3d22c439…de6d
0x34b655…2a6f
4 touches
1 conflict
0x909b34ee…b9e3
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 0xbf78ee7fb5…b5e7fd
Audit this contract →
← previous block·next block →recent activity