← previous blocknext block →recent activity

Analyzing

Block #74,491,786

34 transactions · 24 stateful · 2026-05-14 07:29:35 UTC

Parallelism

65/100

Blocked

71%

Avg conflicts / tx

2.29

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,491,786  ·  34 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xda890365…7972

0xd32edf…ff58

23 touches
66 conflicts

0xa472d565…9fe4

0x3bd359…433a

10 touches
10 conflicts

0x00000000…0003

0x116e7d…d8f1

4 touches
1 conflict

0xab2f6eed…254a

0x188d58…ea8e

4 touches
1 conflict

0xab2f6eed…254b

0x188d58…ea8e

4 touches
1 conflict

0x692a4122…76b8

0x350035…7777

4 touches
1 conflict

0xd06cc746…27e4

0x350035…7777

4 touches
1 conflict

0x00c46468…f328

0x3bd359…433a

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

66 conflicts on slot 0xda890365ee…cb7972

← previous block·next block →recent activity