← previous blocknext block →recent activity
Analyzing
Block #85,726,466
29 transactions · 24 stateful · 2026-07-05 08:41:55 UTC
Parallelism
86/100
Blocked
42%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,726,466 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w29w110w218w319w020w122w325w026w127w228w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc4925de8…b8d9
0xd32edf…ff58
7 touches
6 conflicts
0xc7ac2c0f…f591
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xd45bf713…49a6
0x34b655…2a6f
6 touches
3 conflicts
0xecebc0df…5495
0x34b655…2a6f
6 touches
3 conflicts
0xea2d3331…6e36
0x1b6862…e19c
4 touches
1 conflict
0xf7f6893b…7d2f
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity