← previous blocknext block →recent activity

Analyzing

Block #73,922,543

19 transactions · 15 stateful · 2026-05-11 16:19:53 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.21

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,922,543  ·  19 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

0xee230b20…5a0f

0x34b655…2a6f

14 touches
21 conflicts

0x2aef4269…ad47

0x34b655…2a6f

10 touches
10 conflicts

0x9d652ee8…83ca

0x34b655…2a6f

10 touches
10 conflicts

0x578e7f66…1b56

0x34b655…2a6f

10 touches
10 conflicts

0x4f483049…3cc7

0x34b655…2a6f

10 touches
10 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

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