← previous blocknext block →recent activity
Analyzing
Block #85,132,360
28 transactions · 25 stateful · 2026-07-02 14:43:56 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
1.04
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,132,360 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w08w19w210w311w415w016w122w123w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x366f651e…6100
0x34b655…2a6f
6 touches
3 conflicts
0x379a09c4…259b
0x34b655…2a6f
6 touches
3 conflicts
0x830cb34d…b64f
0x34b655…2a6f
6 touches
3 conflicts
0x97c67486…27fe
0x34b655…2a6f
6 touches
3 conflicts
0xe47478a3…a058
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity