← previous blocknext block →recent activity

Analyzing

Block #73,270,514

15 transactions · 12 stateful · 2026-05-08 15:44:23 UTC

Parallelism

73/100

Blocked

25%

Avg conflicts / tx

0.33

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,270,514  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0xbd7e37a9…9eb5

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xd322b30b…3d0c

0x065c9d…c394

3 touches
1 conflict

0xf68c8f80…fd87

0x065c9d…c394

3 touches
1 conflict

0x645082a0…cd60

0x065c9d…c394

3 touches
1 conflict

0x1a4b4152…0a08

0xaba216…a862

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