← previous blocknext block →recent activity
Analyzing
Block #85,131,569
26 transactions · 25 stateful · 2026-07-02 14:38:39 UTC
Parallelism
69/100
Blocked
48%
Avg conflicts / tx
1.23
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,131,569 · 26 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
2w03w14w26w07w18w29w310w411w513w716w318w219w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
14 touches
21 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x25e3730b…24a9
0x34b655…2a6f
6 touches
3 conflicts
0x3c7520fc…9ca3
0x34b655…2a6f
6 touches
3 conflicts
0x7ae63663…9d94
0x34b655…2a6f
6 touches
3 conflicts
0x9495bffc…46e6
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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