← previous blocknext block →recent activity
Analyzing
Block #86,784,190
70 transactions · 50 stateful · 2026-07-10 06:25:05 UTC
Parallelism
71/100
Blocked
82%
Avg conflicts / tx
2.87
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,784,190 · 70 txs across 20 waves · depth 20
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
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w19w112w213w314w016w119w222w325w426w027w128w258w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0x00000000…0002
0x04fdea…47d7
20 touches
45 conflicts
0x737acb78…fce8
0x34b655…2a6f
18 touches
36 conflicts
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0xc3688185…9b36
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…00c9
0x34b655…2a6f
14 touches
21 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity