← previous blocknext block →recent activity
Analyzing
Block #85,570,951
37 transactions · 28 stateful · 2026-07-04 15:24:50 UTC
Parallelism
78/100
Blocked
64%
Avg conflicts / tx
1.76
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,570,951 · 37 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w38w49w511w630w632w734w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
16 touches
28 conflicts
0x15a8dcd6…2c36
0x34b655…2a6f
16 touches
28 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
16 touches
28 conflicts
0xc7a15219…7745
0xa6afd3…d132
16 touches
28 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
16 touches
28 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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity