← previous blocknext block →recent activity
Analyzing
Block #88,340,369
14 transactions · 14 stateful · 2026-07-17 11:53:04 UTC
Parallelism
86/100
Blocked
14%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,340,369 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44fb0f8a…b7c3
0x34b655…2a6f
4 touches
1 conflict
0xc4de6652…13f4
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x44fb0f8a…b7c4
0x34b655…2a6f
4 touches
1 conflict
0x96821386…3dc2
0x34b655…2a6f
3 touches
1 conflict
0x2538e0fb…0c42
0x34b655…2a6f
2 touches
0 conflicts
0x26dee23d…b18b
0x34b655…2a6f
2 touches
0 conflicts
0x292104fa…5e18
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x44fb0f8ad5…77b7c3
Audit this contract →
← previous block·next block →recent activity