← previous blocknext block →recent activity
Analyzing
Block #88,365,979
23 transactions · 19 stateful · 2026-07-17 14:45:18 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #88,365,979 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w19w010w011w112w213w014w116w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427d1120…4eb1
0x34b655…2a6f
8 touches
6 conflicts
0xa6464996…3af9
0x34b655…2a6f
6 touches
3 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x09a15b10…2639
0x754704…b603
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 0x427d112082…7c4eb1
Audit this contract →
← previous block·next block →recent activity