← previous blocknext block →recent activity

Analyzing

Block #73,491,251

10 transactions · 9 stateful · 2026-05-09 16:13:12 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,491,251  ·  10 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x6bd9b2de…7d72

0x0f2610…0edc

2 touches
0 conflicts

0x1cf46637…3dcb

0x2ae0cf…3d4e

2 touches
0 conflicts

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x4f4bdabd…ffba

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity