Block #73,924,968

← previous blocknext block →recent activity

Analyzing

Block #73,924,968

19 transactions · 17 stateful · 2026-05-11 16:36:01 UTC

Parallelism

63/100

Blocked

65%

Avg conflicts / tx

1.89

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,924,968  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xee230b20…5a0f

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x96844849…b4b0

0x34b655…2a6f

8 touches
6 conflicts

0xc50e4c77…cc13

0x34b655…2a6f

8 touches
6 conflicts

0x37d49489…9309

0x34b655…2a6f

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x4f483049…3cc7

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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity