← previous blocknext block →recent activity

Analyzing

Block #73,348,269

17 transactions · 14 stateful · 2026-05-09 00:21:43 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,348,269  ·  17 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

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x77f58d05…50c4

0x065c9d…c394

2 touches
0 conflicts

0x7d01f1a0…86cc

0x065c9d…c394

2 touches
0 conflicts

0xaa35a2d8…3b23

0x065c9d…c394

2 touches
0 conflicts

0x00000000…000b

0x5075ea…d70f

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity