← previous blocknext block →recent activity

Analyzing

Block #73,660,321

16 transactions · 14 stateful · 2026-05-10 11:00:40 UTC

Parallelism

69/100

Blocked

29%

Avg conflicts / tx

0.63

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,660,321  ·  16 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

0x5c8ebbff…45e1

0xd32edf…ff58

9 touches
10 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x6fe107ed…d12c

0x065c9d…c394

2 touches
0 conflicts

0xb159af88…a9e7

0x065c9d…c394

2 touches
0 conflicts

0xae69c125…2379

0x2a68ba…90c5

2 touches
0 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x38524fae…9deb

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: 0xd32edf66…9fff58

10 conflicts on slot 0x5c8ebbff6b…1945e1

← previous block·next block →recent activity