← previous blocknext block →recent activity

Analyzing

Block #73,648,154

14 transactions · 11 stateful · 2026-05-10 09:38:45 UTC

Parallelism

71/100

Blocked

27%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,648,154  ·  14 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2dbaa2ec…a19c

0x065c9d…c394

3 touches
1 conflict

0x4cbf05c0…05e3

0x065c9d…c394

3 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

2 touches
0 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

2 touches
0 conflicts

0xaed1fa0f…08fa

0x34b655…2a6f

2 touches
0 conflicts

0xeb038f89…31d3

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity