← previous blocknext block →recent activity
Analyzing
Block #86,977,848
10 transactions · 7 stateful · 2026-07-11 03:59:33 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,977,848 · 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
3w04w17w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc05939be…c684
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x2b95e778…d7d0
0x34b655…2a6f
4 touches
1 conflict
0x3f4d2f3d…d3b8
0x34b655…2a6f
4 touches
1 conflict
0x3f4d2f3d…d3b9
0x34b655…2a6f
4 touches
1 conflict
0x53c922c1…1f78
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x5d863b2f…bd28
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
1 conflict on slot 0xc05939becf…86c684
Audit this contract →
← previous block·next block →recent activity