← previous blocknext block →recent activity

Analyzing

Block #73,911,562

13 transactions · 12 stateful · 2026-05-11 15:06:37 UTC

Parallelism

54/100

Blocked

42%

Avg conflicts / tx

1.15

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,911,562  ·  13 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0c52cabc…caba

0x34b655…2a6f

12 touches
15 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

10 touches
10 conflicts

0x4f483049…3cc7

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

10 touches
10 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

10 touches
10 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

15 conflicts on slot 0x0c52cabc02…facaba

← previous block·next block →recent activity