← previous blocknext block →recent activity
Analyzing
Block #85,136,809
24 transactions · 18 stateful · 2026-07-02 15:13:37 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,136,809 · 24 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
2w07w08w19w210w311w412w513w614w716w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x25de453d…9573
0x34b655…2a6f
6 touches
3 conflicts
0x06040b44…e244
0x34b655…2a6f
6 touches
3 conflicts
0x656bd53e…af4e
0x34b655…2a6f
6 touches
3 conflicts
0x7506443a…4820
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0xd3ef5630…0de9
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity