← previous blocknext block →recent activity
Analyzing
Block #87,049,608
13 transactions · 13 stateful · 2026-07-11 11:59:09 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,049,608 · 13 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
7w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x204ab28f…7f15
0x34b655…2a6f
4 touches
1 conflict
0x9d2b7caf…91f9
0x34b655…2a6f
4 touches
1 conflict
0x9d2b7caf…91fa
0x34b655…2a6f
4 touches
1 conflict
0x57c3fa9e…daa7
0x34b655…2a6f
4 touches
1 conflict
0xf95506c7…835d
0x34b655…2a6f
3 touches
1 conflict
0x408e66bb…3d6b
0x34b655…2a6f
2 touches
0 conflicts
0x53b4ef2b…8a05
0x34b655…2a6f
2 touches
0 conflicts
0x6d99ac64…0aa3
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 0x204ab28f84…ac7f15
Audit this contract →
← previous block·next block →recent activity