← previous blocknext block →recent activity
Analyzing
Block #88,351,018
18 transactions · 16 stateful · 2026-07-17 13:04:19 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #88,351,018 · 18 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
2w03w04w05w17w18w29w310w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9834665…e363
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x8b818135…eff8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x62b86e44…980e
0x851145…3f07
6 touches
3 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
4 touches
1 conflict
0x8eed7e30…c1ef
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 0xb983466539…cee363
Audit this contract →
← previous block·next block →recent activity