← previous blocknext block →recent activity

Analyzing

Block #72,817,463

11 transactions · 9 stateful · 2026-05-06 13:29:03 UTC

Parallelism

82/100

Blocked

11%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,817,463  ·  11 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

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0xa5d3f460…30ee

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x80e83c58…945b

0x065c9d…c394

3 touches
1 conflict

0xe09eda07…8dda

0x2a68ba…90c5

2 touches
0 conflicts

0x17e2d2a0…359e

0x34b655…2a6f

2 touches
0 conflicts

0x1b5d2e60…99b5

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: 0x065c9d28…a9c394

1 conflict on slot 0x0b390c6160…02dc07

← previous block·next block →recent activity