← previous blocknext block →recent activity

Analyzing

Block #90,237,050

25 transactions · 21 stateful · 2026-07-25 15:23:55 UTC

Parallelism

72/100

Blocked

52%

Avg conflicts / tx

1.2

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #90,237,050  ·  25 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

0x42dfd084…1eb4

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…00c9

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x9cf9008a…d826

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0xe6e6f436…ddc0

0x34b655…2a6f

6 touches
3 conflicts

0x204ccae2…8dc1

0x34b655…2a6f

4 touches
1 conflict

0xbc612eea…d3de

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 0x42dfd0843c…f21eb4

← previous block·next block →recent activity