← previous blocknext block →recent activity

Analyzing

Block #74,328,974

32 transactions · 20 stateful · 2026-05-13 13:26:04 UTC

Parallelism

66/100

Blocked

60%

Avg conflicts / tx

1.81

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,328,974  ·  32 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xbd875058…1cce

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…0003

0x116e7d…d8f1

6 touches
3 conflicts

0x00000000…0000

0x116e7d…d8f1

6 touches
3 conflicts

0x00000000…0002

0x116e7d…d8f1

6 touches
3 conflicts

0x692a4122…76b8

0x350035…7777

6 touches
3 conflicts

0xb7143610…adc4

0x3bd359…433a

6 touches
3 conflicts

0xab2f6eed…254a

0x188d58…ea8e

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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

55 conflicts on slot 0xbd87505894…d61cce

← previous block·next block →recent activity