← previous blocknext block →recent activity
Analyzing
Block #85,509,896
23 transactions · 19 stateful · 2026-07-04 08:38:16 UTC
Parallelism
65/100
Blocked
58%
Avg conflicts / tx
1.39
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #85,509,896 · 23 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
3w04w17w08w111w213w214w315w318w419w520w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30faf03c…78b1
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xca0f0668…caf3
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x0ab54c30…b88e
0x34b655…2a6f
6 touches
3 conflicts
0xb68e226d…c054
0xa6afd3…d132
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x40970e69…da50
0x69df8a…6292
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
21 conflicts on slot 0x30faf03c2d…0178b1
Audit this contract →
← previous block·next block →recent activity