← previous blocknext block →recent activity
Analyzing
Block #87,723,317
22 transactions · 19 stateful · 2026-07-14 15:05:16 UTC
Parallelism
86/100
Blocked
26%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,723,317 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w09w110w011w117w221w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x255ba9f3…396d
0x34b655…2a6f
6 touches
3 conflicts
0x7525206c…fbd5
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
0xc34f797f…dfaa
0x34b655…2a6f
4 touches
1 conflict
0xeeaba9d3…b491
0x34b655…2a6f
4 touches
1 conflict
0xfecb18c0…01ed
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
3 conflicts on slot 0x255ba9f316…9a396d
Audit this contract →
← previous block·next block →recent activity