← previous blocknext block →recent activity

Analyzing

Block #73,921,154

24 transactions · 23 stateful · 2026-05-11 16:10:38 UTC

Parallelism

58/100

Blocked

61%

Avg conflicts / tx

1.83

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,921,154  ·  24 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xee230b20…5a0f

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

8 touches
6 conflicts

0xef2a8932…1398

0x34b655…2a6f

8 touches
6 conflicts

0x96844849…b4b0

0x34b655…2a6f

8 touches
6 conflicts

0x9be2b99a…a959

0x34b655…2a6f

8 touches
6 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

8 touches
6 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: 0x34b6552d…112a6f

21 conflicts on slot 0xee230b202a…c05a0f

← previous block·next block →recent activity