← previous blocknext block →recent activity
Analyzing
Block #85,166,567
14 transactions · 13 stateful · 2026-07-02 18:31:48 UTC
Parallelism
57/100
Blocked
38%
Avg conflicts / tx
1.07
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,166,567 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w09w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0xd90a674b…29f7
0x34b655…2a6f
8 touches
6 conflicts
0xcc3f7ee8…7924
0x34b655…2a6f
6 touches
3 conflicts
0x1c287db3…e562
0x34b655…2a6f
6 touches
3 conflicts
0x74462c1e…84f3
0x34b655…2a6f
6 touches
3 conflicts
0x7fffd49d…772a
0x34b655…2a6f
6 touches
3 conflicts
0xbf043a30…5829
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity