← previous blocknext block →recent activity

Analyzing

Block #73,922,954

13 transactions · 9 stateful · 2026-05-11 16:22:36 UTC

Parallelism

69/100

Blocked

33%

Avg conflicts / tx

0.54

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,922,954  ·  13 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x3072f752…697f

0xd32edf…ff58

7 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0x8d3dbf80…343b

0x065c9d…c394

2 touches
0 conflicts

0x9b0bf774…ee96

0x065c9d…c394

2 touches
0 conflicts

0xaae4c13e…8e38

0x065c9d…c394

2 touches
0 conflicts

0xf1a20539…f094

0x065c9d…c394

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: 0xd32edf66…9fff58

6 conflicts on slot 0x3072f752d9…97697f

← previous block·next block →recent activity