← previous blocknext block →recent activity

Analyzing

Block #73,204,864

28 transactions · 21 stateful · 2026-05-08 08:27:44 UTC

Parallelism

82/100

Blocked

43%

Avg conflicts / tx

0.82

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,204,864  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xce7bfe5e…5e58

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x55b4ed22…fcc8

0x34b655…2a6f

6 touches
3 conflicts

0xa5fb9779…2384

0x34b655…2a6f

6 touches
3 conflicts

0xf4730a2d…3538

0x34b655…2a6f

6 touches
3 conflicts

0x3064a87c…7beb

0xd32edf…ff58

5 touches
3 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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity