← previous blocknext block →recent activity

Analyzing

Block #73,478,401

19 transactions · 16 stateful · 2026-05-09 14:47:37 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,478,401  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

6 touches
3 conflicts

0xe72962f6…e169

0x8d66a4…3095

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x37cfaf01…4a46

0x34b655…2a6f

4 touches
1 conflict

0x64e30b79…bc29

0x34b655…2a6f

4 touches
1 conflict

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