← previous blocknext block →recent activity
Analyzing
Block #86,957,238
10 transactions · 9 stateful · 2026-07-11 01:41:53 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,957,238 · 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
1w04w05w16w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3c3621c7…3e11
0x34b655…2a6f
6 touches
3 conflicts
0xf60d3c80…c8a7
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8dfef5ae…9361
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xae901867…8085
0x34b655…2a6f
4 touches
1 conflict
0xae901867…8086
0x34b655…2a6f
4 touches
1 conflict
0xb6ed530c…d450
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
3 conflicts on slot 0x3c3621c729…5b3e11
Audit this contract →
← previous block·next block →recent activity