← previous blocknext block →recent activity
Analyzing
Block #86,709,235
35 transactions · 32 stateful · 2026-07-09 22:04:22 UTC
Parallelism
69/100
Blocked
66%
Avg conflicts / tx
1.91
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #86,709,235 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w38w49w510w011w112w213w314w415w516w322w124w425w526w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
12 touches
15 conflicts
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x48fb2063…4025
0x34b655…2a6f
8 touches
6 conflicts
0x548145a9…cfce
0x34b655…2a6f
8 touches
6 conflicts
0x63b15849…80b2
0x34b655…2a6f
8 touches
6 conflicts
0xcffc8fcf…ff81
0x34b655…2a6f
8 touches
6 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: 0x04fdeac2…f747d7
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity