← previous blocknext block →recent activity

Analyzing

Block #73,811,523

23 transactions · 14 stateful · 2026-05-11 04:00:18 UTC

Parallelism

65/100

Blocked

57%

Avg conflicts / tx

0.78

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,811,523  ·  23 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

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x64cc056c…3a7b

0xd32edf…ff58

7 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0x0175b7a6…1dba

0x6c4bfa…a540

4 touches
1 conflict

0x831d4050…016a

0x065c9d…c394

4 touches
1 conflict

0xa7f5e427…3b13

0x6c4bfa…a540

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

10 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity