← previous blocknext block →recent activity

Analyzing

Block #73,705,305

18 transactions · 14 stateful · 2026-05-10 16:04:13 UTC

Parallelism

56/100

Blocked

50%

Avg conflicts / tx

1.28

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,705,305  ·  18 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

0xa91c899f…6ee3

0x34b655…2a6f

14 touches
21 conflicts

0x462d8e25…1e49

0x34b655…2a6f

12 touches
15 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

10 touches
10 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x5d70606a…1d53

0x34b655…2a6f

10 touches
10 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

8 touches
6 conflicts

0x57de3828…3fbb

0x34b655…2a6f

8 touches
6 conflicts

0x908d4442…2c4b

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 0xa91c899f02…fa6ee3

← previous block·next block →recent activity