← previous blocknext block →recent activity

Analyzing

Block #73,920,838

14 transactions · 13 stateful · 2026-05-11 16:08:32 UTC

Parallelism

79/100

Blocked

46%

Avg conflicts / tx

0.79

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,920,838  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xb1dcb4b3…4b74

0x34b655…2a6f

6 touches
3 conflicts

0xdd75d5ec…8936

0xd32edf…ff58

5 touches
3 conflicts

0x0b0d3b45…a368

0x34b655…2a6f

4 touches
1 conflict

0x1319ae2c…7f9a

0x34b655…2a6f

4 touches
1 conflict

0x25de453d…9573

0x34b655…2a6f

4 touches
1 conflict

0x4f483049…3cc7

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: 0x34b6552d…112a6f

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity