← previous blocknext block →recent activity
Analyzing
Block #86,806,931
40 transactions · 39 stateful · 2026-07-10 08:57:01 UTC
Parallelism
63/100
Blocked
59%
Avg conflicts / tx
2.6
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,806,931 · 40 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w07w08w09w010w112w013w114w215w316w417w518w619w722w626w127w128w829w930w231w233w536w1237w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
20 touches
45 conflicts
0x92385428…6941
0x34b655…2a6f
16 touches
28 conflicts
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x8d888c90…5479
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x85ec9605…9fdd
0x34b655…2a6f
10 touches
10 conflicts
0x890eac6e…1c0d
0x34b655…2a6f
10 touches
10 conflicts
0x9e3f5c49…42e1
0x34b655…2a6f
10 touches
10 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
45 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity