← previous blocknext block →recent activity
Analyzing
Block #88,183,848
23 transactions · 21 stateful · 2026-07-16 18:26:19 UTC
Parallelism
61/100
Blocked
48%
Avg conflicts / tx
1.3
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #88,183,848 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w17w28w39w414w518w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0x4dc6cd61…f674
0x34b655…2a6f
8 touches
6 conflicts
0xa98ae84b…6741
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7743
0x34b655…2a6f
4 touches
1 conflict
0x70b7b52e…7744
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity