Block #73,374,940

← previous blocknext block →recent activity

Analyzing

Block #73,374,940

11 transactions · 10 stateful · 2026-05-09 03:19:09 UTC

Parallelism

82/100

Blocked

10%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,374,940  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x036f3c7e…6b79

0x34b655…2a6f

2 touches
0 conflicts

0x10814d14…cdda

0x34b655…2a6f

2 touches
0 conflicts

0x13e2f506…7d16

0x34b655…2a6f

2 touches
0 conflicts

0x1bc9b1ca…85ef

0x34b655…2a6f

2 touches
0 conflicts

0x20ac0567…c954

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity