← previous blocknext block →recent activity
Analyzing
Block #86,245,732
26 transactions · 21 stateful · 2026-07-07 18:25:06 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,245,732 · 26 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
1w02w17w08w111w217w018w119w222w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1e9a8e72…7138
0x43cf54…7777
6 touches
3 conflicts
0x3ff37a80…4f37
0xd32edf…ff58
5 touches
3 conflicts
0x53897bdd…275d
0x34b655…2a6f
4 touches
1 conflict
0x62fb2b24…4921
0x34b655…2a6f
4 touches
1 conflict
0x8e1318fe…3399
0x34b655…2a6f
4 touches
1 conflict
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0xcda18b0b…6a4c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity