← previous blocknext block →recent activity
Analyzing
Block #85,170,890
27 transactions · 21 stateful · 2026-07-02 19:00:33 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.22
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,170,890 · 27 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
2w03w16w07w112w013w114w215w316w417w518w619w726w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
6 touches
3 conflicts
0xa457c06e…2f06
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xdaa23c10…5c68
0x34b655…2a6f
6 touches
3 conflicts
0xff915e51…060c
0x34b655…2a6f
6 touches
3 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
6 touches
3 conflicts
0x16b3a441…13db
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity