← previous blocknext block →recent activity
Analyzing
Block #85,914,269
20 transactions · 18 stateful · 2026-07-06 05:32:25 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,914,269 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w17w010w211w015w116w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
8 touches
6 conflicts
0xa14c51c5…1146
0x34b655…2a6f
8 touches
6 conflicts
0x36d07801…a7d7
0x34b655…2a6f
6 touches
3 conflicts
0x6c595e56…d5ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e4b5149…c444
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0x66f473d3…2d03
0xa6afd3…d132
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity