← previous blocknext block →recent activity
Analyzing
Block #85,777,364
24 transactions · 18 stateful · 2026-07-05 14:20:26 UTC
Parallelism
88/100
Blocked
44%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,777,364 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w19w010w112w013w115w121w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66f473d3…2d03
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x518f2037…e422
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xfe496e2a…ea17
0x34b655…2a6f
4 touches
1 conflict
0xda2ee2e7…968a
0x34b655…2a6f
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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity