← previous blocknext block →recent activity
Analyzing
Block #87,050,922
13 transactions · 10 stateful · 2026-07-11 12:07:52 UTC
Parallelism
77/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,050,922 · 13 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
6w07w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd38f4e6…586c
0x34b655…2a6f
6 touches
3 conflicts
0x619c81de…01b4
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x6f7775d0…a8b4
0x34b655…2a6f
4 touches
1 conflict
0x7139bf32…c881
0x34b655…2a6f
4 touches
1 conflict
0x1af19f5c…aee2
0x34b655…2a6f
4 touches
1 conflict
0xed4604d7…11d2
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 0xdd38f4e69f…fd586c
Audit this contract →
← previous block·next block →recent activity