← previous blocknext block →recent activity
Analyzing
Block #86,926,214
15 transactions · 12 stateful · 2026-07-10 22:14:39 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,926,214 · 15 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
4w05w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa248a5dd…4a69
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xbdf1e736…db04
0x34b655…2a6f
4 touches
1 conflict
0xe60e9000…c058
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0d05c2b3…bd7e
0x34b655…2a6f
4 touches
1 conflict
0x0d05c2b3…bd7f
0x34b655…2a6f
4 touches
1 conflict
0x5f14622f…73ee
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 0xa248a5dd13…914a69
Audit this contract →
← previous block·next block →recent activity