← previous blocknext block →recent activity
Analyzing
Block #85,353,530
30 transactions · 24 stateful · 2026-07-03 15:17:10 UTC
Parallelism
77/100
Blocked
50%
Avg conflicts / tx
1.03
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,353,530 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w210w011w112w213w314w415w516w617w326w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
8 touches
6 conflicts
0xaae6463e…bfcc
0x34b655…2a6f
8 touches
6 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
8 touches
6 conflicts
0x1da60af2…3010
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xf4150f34…bfea
0x34b655…2a6f
8 touches
6 conflicts
0xe6805ef8…e22e
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity