← previous blocknext block →recent activity
Analyzing
Block #87,066,699
14 transactions · 14 stateful · 2026-07-11 13:53:12 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,066,699 · 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
2w03w14w25w06w17w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd1952ceb…56be
0x34b655…2a6f
6 touches
3 conflicts
0xb88e5f26…1ca6
0x34b655…2a6f
6 touches
3 conflicts
0x20b61653…f867
0x34b655…2a6f
6 touches
3 conflicts
0xa27042a8…2d2e
0x34b655…2a6f
4 touches
1 conflict
0xceb535f3…19cf
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
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity