← previous blocknext block →recent activity

Analyzing

Block #73,804,911

8 transactions · 7 stateful · 2026-05-11 03:16:16 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,804,911  ·  8 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x0e8a2bd3…ef4c

0x34b655…2a6f

4 touches
1 conflict

0x0fa5e7bf…a4da

0x34b655…2a6f

4 touches
1 conflict

0x1319ae2c…7f9a

0x34b655…2a6f

4 touches
1 conflict

0x5de96bd3…c60c

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xac8e97a0…8426

0x34b655…2a6f

4 touches
1 conflict

0xb378025c…30cf

0x34b655…2a6f

4 touches
1 conflict

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

1 conflict on slot 0xc6417de023…802191

← previous block·next block →recent activity