← previous blocknext block →recent activity

Analyzing

Block #73,476,207

10 transactions · 9 stateful · 2026-05-09 14:33:02 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,476,207  ·  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

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0acfd1d4…f99f

0x065c9d…c394

2 touches
0 conflicts

0x05b1f4af…b126

0x34b655…2a6f

2 touches
0 conflicts

0x0de7749d…5bef

0x34b655…2a6f

2 touches
0 conflicts

0x0f729063…d5e9

0x34b655…2a6f

2 touches
0 conflicts

0x206a4507…e6c3

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