← previous blocknext block →recent activity
Analyzing
Block #85,130,316
38 transactions · 30 stateful · 2026-07-02 14:30:16 UTC
Parallelism
89/100
Blocked
43%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,130,316 · 38 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
4w06w17w08w010w012w113w215w017w218w319w020w121w222w325w026w128w129w134w235w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fffd49d…772a
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x264f7d7d…8444
0x34b655…2a6f
8 touches
6 conflicts
0x10aad9f2…9dfc
0xd32edf…ff58
7 touches
6 conflicts
0x67d8b378…f2f8
0x34b655…2a6f
7 touches
6 conflicts
0xe727ab72…768b
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
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
6 conflicts on slot 0x7fffd49db6…f8772a
Audit this contract →
← previous block·next block →recent activity