← previous blocknext block →recent activity
Analyzing
Block #88,342,128
17 transactions · 17 stateful · 2026-07-17 12:04:49 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #88,342,128 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w27w38w413w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f900be0…cd6e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x017975b8…fd4c
0x34b655…2a6f
6 touches
3 conflicts
0x3a565e61…7dbb
0x34b655…2a6f
4 touches
1 conflict
0x4e970d38…d1c4
0x34b655…2a6f
4 touches
1 conflict
0x4fa49ab2…3116
0x34b655…2a6f
4 touches
1 conflict
0x6d597594…10d1
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 0x6f900be04d…4ccd6e
Audit this contract →
← previous block·next block →recent activity