← previous blocknext block →recent activity
Analyzing
Block #88,157,665
27 transactions · 25 stateful · 2026-07-16 15:30:45 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #88,157,665 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w19w010w111w212w313w414w515w617w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xed4a0d72…065f
0x34b655…2a6f
6 touches
3 conflicts
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x6f94f9d4…2afd
0x34b655…2a6f
4 touches
1 conflict
0x27a78688…b891
0x34b655…2a6f
4 touches
1 conflict
0x785705a8…33e5
0x34b655…2a6f
4 touches
1 conflict
0x789a9e34…857d
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