← previous blocknext block →recent activity
Analyzing
Block #88,137,764
19 transactions · 17 stateful · 2026-07-16 13:17:26 UTC
Parallelism
74/100
Blocked
41%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,137,764 · 19 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
1w06w08w09w110w111w212w114w316w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25ff7717…d4af
0x34b655…2a6f
8 touches
6 conflicts
0x5402bc82…660b
0x34b655…2a6f
6 touches
3 conflicts
0x557aa673…6559
0x851145…3f07
4 touches
1 conflict
0xf9e23360…8ef7
0x34b655…2a6f
4 touches
1 conflict
0xfe2c1082…db16
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x44fb0f8a…b7c3
0x34b655…2a6f
4 touches
1 conflict
0x44fb0f8a…b7c4
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
6 conflicts on slot 0x25ff77178c…2ad4af
Audit this contract →
← previous block·next block →recent activity