← previous blocknext block →recent activity

Analyzing

Block #73,681,307

12 transactions · 11 stateful · 2026-05-10 13:22:29 UTC

Parallelism

75/100

Blocked

27%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,681,307  ·  12 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

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0xb6b74ae0…8d5e

0xea1b8e…c5ec

4 touches
1 conflict

0x57bc5ac6…82a3

0x1efe02…37d6

2 touches
0 conflicts

0xea63e6e2…1ee1

0x1efe02…37d6

2 touches
0 conflicts

0x00000000…0002

0xab3526…fa38

2 touches
0 conflicts

0x26df9e1d…74a2

0xea1b8e…c5ec

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

3 conflicts on slot 0x0ac3194537…8f2c72

← previous block·next block →recent activity