← previous blocknext block →recent activity
Analyzing
Block #86,848,834
26 transactions · 21 stateful · 2026-07-10 13:37:13 UTC
Parallelism
69/100
Blocked
52%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,848,834 · 26 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
1w02w15w26w310w011w112w213w314w415w518w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x19795ad6…4a16
0x34b655…2a6f
10 touches
10 conflicts
0x2130a548…c1de
0x34b655…2a6f
10 touches
10 conflicts
0x3230277c…ef39
0xc8689a…ee79
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x38c6ff01…689f
0x34b655…2a6f
8 touches
6 conflicts
0x414ca622…37ab
0x34b655…2a6f
8 touches
6 conflicts
0x574628e9…dcc3
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: Perpl
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity