← previous blocknext block →recent activity

Analyzing

Block #73,499,631

19 transactions · 15 stateful · 2026-05-09 17:08:56 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,499,631  ·  19 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

6 touches
3 conflicts

0x3638e1ad…ec0e

0x34b655…2a6f

6 touches
3 conflicts

0x57de3828…3fbb

0x34b655…2a6f

6 touches
3 conflicts

0xedb848fe…6534

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x23951077…539b

0x34b655…2a6f

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

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

3 conflicts on slot 0x8db1e0f2ad…b02fcf

← previous block·next block →recent activity