← previous blocknext block →recent activity
Analyzing
Block #87,056,833
14 transactions · 11 stateful · 2026-07-11 12:47:24 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,056,833 · 14 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
5w06w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b28ab0…40d1
0x34b655…2a6f
6 touches
3 conflicts
0xce3de73c…ae35
0x34b655…2a6f
6 touches
3 conflicts
0x6757b643…ebef
0x34b655…2a6f
5 touches
3 conflicts
0x25957369…c648
0x34b655…2a6f
4 touches
1 conflict
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x36638a70…343b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6122676a…1970
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 0xb7b28ab0c6…fd40d1
Audit this contract →
← previous block·next block →recent activity