← previous blocknext block →recent activity
Analyzing
Block #86,624,334
41 transactions · 31 stateful · 2026-07-09 12:36:15 UTC
Parallelism
85/100
Blocked
58%
Avg conflicts / tx
1.02
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,624,334 · 41 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w116w017w118w219w320w421w524w430w233w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
12 touches
15 conflicts
0xad180d12…5569
0xd32edf…ff58
9 touches
10 conflicts
0x38d19a60…c141
0x34b655…2a6f
8 touches
6 conflicts
0x3a2a8323…3f40
0x34b655…2a6f
8 touches
6 conflicts
0x4e43bdc7…ce29
0x34b655…2a6f
8 touches
6 conflicts
0x6b2ba712…0214
0x34b655…2a6f
8 touches
6 conflicts
0x7523ad90…2ba5
0x34b655…2a6f
8 touches
6 conflicts
0x8a5ced1c…3b29
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
15 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity