← previous blocknext block →recent activity

Analyzing

Block #86,136,378

35 transactions · 26 stateful · 2026-07-07 06:14:56 UTC

Parallelism

91/100

Blocked

19%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,136,378  ·  35 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xc96dc136…40dc

0xd32edf…ff58

5 touches
3 conflicts

0x6b405d1c…29a4

0x851145…3f07

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0x776b206d…6cf9

0x3bd359…433a

2 touches
0 conflicts

0xf8127de7…d5ec

0x3bd359…433a

2 touches
0 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: FastLane: FastLaneAuctionHandler

3 conflicts on slot 0xc96dc13668…a740dc

← previous block·next block →recent activity