← previous blocknext block →recent activity
Analyzing
Block #85,414,181
37 transactions · 31 stateful · 2026-07-03 22:01:08 UTC
Parallelism
81/100
Blocked
61%
Avg conflicts / tx
1.08
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,414,181 · 37 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w37w48w39w010w111w212w317w018w119w220w321w428w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x30faf03c…78b1
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
8 touches
6 conflicts
0xdb9345e3…76bf
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x7d4f80a4…bb1a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity