← previous blocknext block →recent activity
Analyzing
Block #85,570,366
24 transactions · 20 stateful · 2026-07-04 15:20:57 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,570,366 · 24 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
2w05w16w27w08w110w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x757b0543…e087
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
8 touches
6 conflicts
0xc6ed530e…fa7d
0x34b655…2a6f
8 touches
6 conflicts
0xd5e4013d…a383
0x34b655…2a6f
8 touches
6 conflicts
0x45597879…8174
0x34b655…2a6f
8 touches
6 conflicts
0xf4150f34…bfea
0x34b655…2a6f
8 touches
6 conflicts
0x2c8bf7d9…3cc7
0xc8689a…ee79
8 touches
6 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 0x757b054398…dbe087
Audit this contract →
← previous block·next block →recent activity