← previous blocknext block →recent activity
Analyzing
Block #86,386,006
28 transactions · 25 stateful · 2026-07-08 10:02:01 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
1.11
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,386,006 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w010w111w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000a
0x90c374…be45
16 touches
28 conflicts
0x00000000…000b
0x90c374…be45
16 touches
28 conflicts
0x64d0c031…0a72
0xd32edf…ff58
5 touches
3 conflicts
0x27a04273…27c5
0x065c9d…c394
2 touches
0 conflicts
0x9997cc92…2f25
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
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: 0x90c3747c…0ebe45
28 conflicts on slot 0x0000000000…00000a
Audit this contract →
← previous block·next block →recent activity