← previous blocknext block →recent activity
Analyzing
Block #88,160,536
21 transactions · 19 stateful · 2026-07-16 15:49:58 UTC
Parallelism
86/100
Blocked
21%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #88,160,536 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w07w18w011w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x250c1933…f991
0x34b655…2a6f
6 touches
3 conflicts
0x09897b3d…24c0
0x34b655…2a6f
4 touches
1 conflict
0x185e731c…9ced
0x34b655…2a6f
4 touches
1 conflict
0x1d1013ce…2480
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5b353877…605d
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
3 conflicts on slot 0x250c193342…1ff991
Audit this contract →
← previous block·next block →recent activity