← previous blocknext block →recent activity
Analyzing
Block #87,055,084
10 transactions · 9 stateful · 2026-07-11 12:35:42 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,055,084 · 10 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
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4b9af402…c2d8
0x34b655…2a6f
4 touches
1 conflict
0x552ac70a…d74b
0x34b655…2a6f
4 touches
1 conflict
0xb367dbbf…add9
0x34b655…2a6f
4 touches
1 conflict
0xeee86caf…3105
0x34b655…2a6f
4 touches
1 conflict
0xb367dbbf…adda
0x34b655…2a6f
4 touches
1 conflict
0x655e51cc…ca7e
0x34b655…2a6f
3 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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity