← previous blocknext block →recent activity

Analyzing

Block #74,392,048

21 transactions · 16 stateful · 2026-05-13 20:25:42 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.14

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,392,048  ·  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

0x9cd9f1eb…423e

0xd32edf…ff58

13 touches
21 conflicts

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xa486f342…64d5

0x34b655…2a6f

4 touches
1 conflict

0x8fdebdb1…d449

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x91220b8f…7a03

0x1b6862…e19c

2 touches
0 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

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

21 conflicts on slot 0x9cd9f1ebb8…96423e

← previous block·next block →recent activity