← previous blocknext block →recent activity

Analyzing

Block #73,837,521

9 transactions · 4 stateful · 2026-05-11 06:53:17 UTC

Parallelism

78/100

Blocked

25%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,837,521  ·  9 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

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa5e1d712…943d

0x065c9d…c394

3 touches
1 conflict

0xfb1e271e…5a6a

0x065c9d…c394

3 touches
1 conflict

0x28c180e1…f1e2

0x34b655…2a6f

2 touches
0 conflicts

0x2a1e963e…2c91

0x34b655…2a6f

2 touches
0 conflicts

0x2d6d9781…f1fa

0x34b655…2a6f

2 touches
0 conflicts

0x4d3e58e0…a2d7

0x34b655…2a6f

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity