← previous blocknext block →recent activity
Analyzing
Block #85,191,523
18 transactions · 16 stateful · 2026-07-02 21:17:58 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,191,523 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w08w09w110w213w115w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x274b85f7…c526
0x34b655…2a6f
4 touches
1 conflict
0x97fe3267…5e87
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x39d92746…1846
0x065c9d…c394
3 touches
1 conflict
0x04ac167f…4394
0xd32edf…ff58
3 touches
1 conflict
0x765569e1…56c2
0x5afd3e…7620
2 touches
0 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
3 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity