← previous blocknext block →recent activity
Analyzing
Block #87,257,107
10 transactions · 9 stateful · 2026-07-12 11:06:39 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,257,107 · 10 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
5w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6aea3f64…bb1f
0x34b655…2a6f
4 touches
1 conflict
0x7c11df38…2f2c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0d05e294…dfe5
0x34b655…2a6f
4 touches
1 conflict
0x8cf3d245…1d0d
0x69df8a…6292
2 touches
0 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
2 touches
0 conflicts
0xdb067026…9eb8
0x69df8a…6292
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 0x6aea3f6436…44bb1f
Audit this contract →
← previous block·next block →recent activity