← previous blocknext block →recent activity
Analyzing
Block #86,250,293
25 transactions · 22 stateful · 2026-07-07 18:55:37 UTC
Parallelism
88/100
Blocked
41%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,250,293 · 25 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
1w02w03w14w05w16w27w08w19w212w013w118w119w221w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x202c03eb…cf33
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa3d7b5e3…291f
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x11998eac…f9a6
0x1b6862…e19c
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: 0x681e908b…e1ae09
3 conflicts on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity