← previous blocknext block →recent activity

Analyzing

Block #93,188,002

17 transactions · 15 stateful · 2026-08-04 23:08:58 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.76

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #93,188,002  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x3b6c3926…a378

0xd32edf…ff58

7 touches
6 conflicts

0x8590b692…b267

0x34b655…2a6f

6 touches
3 conflicts

0x1a69c7c5…09cc

0x34b655…2a6f

4 touches
1 conflict

0x231ccc13…a7c6

0x34b655…2a6f

4 touches
1 conflict

0x27034002…2f27

0x34b655…2a6f

4 touches
1 conflict

0x28db94da…027c

0x34b655…2a6f

4 touches
1 conflict

0x2fd12b6c…02cc

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

6 conflicts on slot 0x3b6c3926d8…02a378

← previous block·next block →recent activity