← previous blocknext block →recent activity

Analyzing

Block #73,920,921

32 transactions · 29 stateful · 2026-05-11 16:09:05 UTC

Parallelism

75/100

Blocked

48%

Avg conflicts / tx

1.38

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,920,921  ·  32 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

12 touches
15 conflicts

0x4f483049…3cc7

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

12 touches
15 conflicts

0xac8e97a0…8426

0x34b655…2a6f

12 touches
15 conflicts

0xbc3d6b37…2215

0x34b655…2a6f

12 touches
15 conflicts

0x03df3a18…58e7

0x34b655…2a6f

12 touches
15 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

28 conflicts on slot 0xee230b202a…c05a0f

← previous block·next block →recent activity