← previous blocknext block →recent activity
Analyzing
Block #85,133,437
29 transactions · 23 stateful · 2026-07-02 14:51:08 UTC
Parallelism
72/100
Blocked
57%
Avg conflicts / tx
1.31
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,133,437 · 29 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
1w03w17w08w19w210w311w412w513w614w719w126w527w6
- 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
10 touches
10 conflicts
0x5b353877…605d
0x34b655…2a6f
10 touches
10 conflicts
0x76195b9b…6629
0x34b655…2a6f
10 touches
10 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
10 touches
10 conflicts
0xd6418d68…bdc5
0x34b655…2a6f
10 touches
10 conflicts
0xdc8d4ee0…def3
0x34b655…2a6f
10 touches
10 conflicts
0xe47478a3…a058
0x34b655…2a6f
10 touches
10 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