Block #73,343,569

← previous blocknext block →recent activity

Analyzing

Block #73,343,569

15 transactions · 14 stateful · 2026-05-08 23:50:27 UTC

Parallelism

67/100

Blocked

29%

Avg conflicts / tx

0.87

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,343,569  ·  15 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

0xf2f76ab3…623e

0x2a68ba…90c5

10 touches
10 conflicts

0x6f08361d…bda6

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x33b2cbd3…91f2

0x065c9d…c394

2 touches
0 conflicts

0xc0e9c47b…abaa

0x21ed3b…2a88

2 touches
0 conflicts

0xc0e9c47b…abad

0x21ed3b…2a88

2 touches
0 conflicts

0xbdff944d…447e

0x2a68ba…90c5

2 touches
0 conflicts

0x01a89030…f786

0x368ee5…7ca4

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity