← previous blocknext block →recent activity
Analyzing
Block #88,160,467
23 transactions · 19 stateful · 2026-07-16 15:49:30 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,160,467 · 23 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
3w05w06w18w09w110w212w315w421w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25ff7717…d4af
0x34b655…2a6f
10 touches
10 conflicts
0x424934c8…f2f1
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48315f67…c1a6
0x34b655…2a6f
4 touches
1 conflict
0x4be0b838…9dd7
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x25ff77178c…2ad4af
Audit this contract →
← previous block·next block →recent activity