← previous blocknext block →recent activity

Analyzing

Block #73,483,386

11 transactions · 8 stateful · 2026-05-09 15:20:45 UTC

Parallelism

55/100

Blocked

50%

Avg conflicts / tx

0.91

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,483,386  ·  11 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

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0x57de3828…3fbb

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xedb848fe…6534

0x34b655…2a6f

10 touches
10 conflicts

0xacd10bf4…2244

0x34b655…2a6f

6 touches
3 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0xa91c899f…6ee3

0x34b655…2a6f

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

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: 0xc8689a47…62ee79

10 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity