← previous blocknext block →recent activity
Analyzing
Block #85,973,379
35 transactions · 28 stateful · 2026-07-06 12:06:37 UTC
Parallelism
86/100
Blocked
43%
Avg conflicts / tx
0.51
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,973,379 · 35 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w28w39w010w111w214w117w018w120w321w031w132w233w334w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd41c04a1…154d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x6bc6a39f…1940
0xd32edf…ff58
5 touches
3 conflicts
0x8c962d08…9e24
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x3af0dd8e…0023
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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