← previous blocknext block →recent activity
Analyzing
Block #86,238,701
24 transactions · 18 stateful · 2026-07-07 17:38:04 UTC
Parallelism
83/100
Blocked
39%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,238,701 · 24 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
1w02w13w28w110w014w115w216w320w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6f4ba47e…0aa9
0xd32edf…ff58
5 touches
3 conflicts
0x216ffe66…1f94
0x34b655…2a6f
4 touches
1 conflict
0x5a9f700f…6470
0x34b655…2a6f
4 touches
1 conflict
0x5ccbdfb6…3e06
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5317
0x34b655…2a6f
4 touches
1 conflict
0x5e782d17…5318
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity