Block #73,476,315

← previous blocknext block →recent activity

Analyzing

Block #73,476,315

11 transactions · 10 stateful · 2026-05-09 14:33:44 UTC

Parallelism

55/100

Blocked

40%

Avg conflicts / tx

0.91

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,476,315  ·  11 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

0x6f08361d…bda6

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x9fd4fcf6…fb3a

0x065c9d…c394

3 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

2 touches
0 conflicts

0xc9e97522…3519

0x2a68ba…90c5

2 touches
0 conflicts

0x1a4b4152…0a08

0x6c4bfa…a540

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

10 conflicts on slot 0x6f08361da9…89bda6

← previous block·next block →recent activity