← previous blocknext block →recent activity

Analyzing

Block #95,295,587

32 transactions · 13 stateful · 2026-08-12 08:15:46 UTC

Parallelism

81/100

Blocked

54%

Avg conflicts / tx

0.53

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,295,587  ·  32 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x1ca7ae89…6cdb

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0004

0x63e48b…53f2

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

4 touches
1 conflict

0x00000000…0002

0x63e48b…53f2

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

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: FastLane: FastLaneAuctionHandler

15 conflicts on slot 0x1ca7ae89bc…9b6cdb

← previous block·next block →recent activity