← previous blocknext block →recent activity
Analyzing
Block #85,131,271
23 transactions · 22 stateful · 2026-07-02 14:36:40 UTC
Parallelism
70/100
Blocked
64%
Avg conflicts / tx
1.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,131,271 · 23 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
1w02w13w24w36w07w08w19w210w311w412w513w614w515w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x3230277c…ef39
0xc8689a…ee79
6 touches
3 conflicts
0x85029cd6…857d
0x34b655…2a6f
6 touches
3 conflicts
0xa0f905a8…5612
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
0x34b655…2a6f
6 touches
3 conflicts
0xcffc17bc…3544
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
21 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity