← previous blocknext block →recent activity

Analyzing

Block #73,348,259

36 transactions · 28 stateful · 2026-05-09 00:21:39 UTC

Parallelism

78/100

Blocked

46%

Avg conflicts / tx

0.83

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,348,259  ·  36 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x22e295f5…1bef

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xde59a7e6…4c20

0xd32edf…ff58

7 touches
6 conflicts

0xbdff944d…447e

0x2a68ba…90c5

6 touches
3 conflicts

0x0f9b918b…212d

0x34b655…2a6f

6 touches
3 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 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 0x22e295f5d8…ac1bef

← previous block·next block →recent activity