← previous blocknext block →recent activity

Analyzing

Block #73,483,919

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

Parallelism

71/100

Blocked

27%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,483,919  ·  17 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

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

10 touches
10 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

10 touches
10 conflicts

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0xb98b9e9d…a785

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

2 touches
0 conflicts

0x5a930882…c28a

0x5afd3e…7620

2 touches
0 conflicts

0xcd182cd6…d598

0x5afd3e…7620

2 touches
0 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: 0x754704bc…afb603

10 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity