← previous blocknext block →recent activity

Analyzing

Block #73,795,644

9 transactions · 9 stateful · 2026-05-11 02:13:54 UTC

Parallelism

44/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,795,644  ·  9 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

8 touches
6 conflicts

0x7117db59…45cd

0x34b655…2a6f

8 touches
6 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

6 touches
3 conflicts

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

6 touches
3 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

6 conflicts on slot 0x8db1e0f2ad…b02fcf

← previous block·next block →recent activity