Block #73,223,818

← previous blocknext block →recent activity

Analyzing

Block #73,223,818

13 transactions · 12 stateful · 2026-05-08 10:33:51 UTC

Parallelism

69/100

Blocked

25%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,223,818  ·  13 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

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2628d77d…9a6e

0x065c9d…c394

4 touches
1 conflict

0xf96f3ed5…9cb7

0x065c9d…c394

3 touches
1 conflict

0x8d0dfe2c…3345

0x2a68ba…90c5

2 touches
0 conflicts

0xbdff944d…447e

0x2a68ba…90c5

2 touches
0 conflicts

0x00000000…000b

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 0x0b390c6160…02dc07

← previous block·next block →recent activity