← previous blocknext block →recent activity
Analyzing
Block #86,934,090
11 transactions · 11 stateful · 2026-07-10 23:07:15 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,934,090 · 11 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
5w06w17w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d43cc69…6f83
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xce3de73c…ae36
0x34b655…2a6f
4 touches
1 conflict
0x0a6a5b44…d0e5
0x34b655…2a6f
4 touches
1 conflict
0xc2e9d563…9c7f
0x34b655…2a6f
4 touches
1 conflict
0xc2e9d563…9c80
0x34b655…2a6f
4 touches
1 conflict
0xce3de73c…ae35
0x34b655…2a6f
4 touches
1 conflict
0x48b8d2e5…3f2f
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 0x0d43cc69f6…c46f83
Audit this contract →
← previous block·next block →recent activity