← previous blocknext block →recent activity

Analyzing

Block #73,918,911

17 transactions · 16 stateful · 2026-05-11 15:55:43 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,918,911  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

6 touches
3 conflicts

0x4f483049…3cc7

0x34b655…2a6f

6 touches
3 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xac8e97a0…8426

0x34b655…2a6f

6 touches
3 conflicts

0xbc3d6b37…2215

0x34b655…2a6f

6 touches
3 conflicts

0x23951077…539b

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

3 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity