← previous blocknext block →recent activity

Analyzing

Block #73,506,194

10 transactions · 9 stateful · 2026-05-09 17:52:43 UTC

Parallelism

50/100

Blocked

44%

Avg conflicts / tx

0.9

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,506,194  ·  10 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

0x868859b9…3db5

0x34b655…2a6f

8 touches
6 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x57de3828…3fbb

0x34b655…2a6f

8 touches
6 conflicts

0x5d70606a…1d53

0x34b655…2a6f

6 touches
3 conflicts

0x77905798…fe3d

0x34b655…2a6f

6 touches
3 conflicts

0x888889e8…5f32

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

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 0x868859b9d6…413db5

← previous block·next block →recent activity