← previous blocknext block →recent activity

Analyzing

Block #74,196,646

21 transactions · 15 stateful · 2026-05-12 22:46:07 UTC

Parallelism

67/100

Blocked

60%

Avg conflicts / tx

1.19

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,196,646  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xcbbf0305…c03a

0xd32edf…ff58

13 touches
21 conflicts

0xd53220ed…473a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

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

21 conflicts on slot 0xcbbf030570…bdc03a

← previous block·next block →recent activity