← previous blocknext block →recent activity
Analyzing
Block #86,950,260
10 transactions · 10 stateful · 2026-07-11 00:55:15 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,950,260 · 10 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
2w03w14w26w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1ac
0xb1dbf0…c0d3
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xa412324b…90aa
0x34b655…2a6f
6 touches
3 conflicts
0xa412324b…90ab
0x34b655…2a6f
6 touches
3 conflicts
0xd1db601b…c70d
0x34b655…2a6f
6 touches
3 conflicts
0x0335ae80…8414
0xb1dbf0…c0d3
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: 0xb1dbf05f…b1c0d3
3 conflicts on slot 0x8a35acfbc1…6bd1ac
Audit this contract →
← previous block·next block →recent activity