← previous blocknext block →recent activity

Analyzing

Block #73,926,067

30 transactions · 20 stateful · 2026-05-11 16:43:20 UTC

Parallelism

77/100

Blocked

65%

Avg conflicts / tx

1.43

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,926,067  ·  30 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

0x0271549c…9eea

0xd32edf…ff58

13 touches
21 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

10 touches
10 conflicts

0xe4f0f159…0c50

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xb142d1c0…fe1e

0x34b655…2a6f

8 touches
6 conflicts

0xac8e97a0…8426

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0xbc3d6b37…2215

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

21 conflicts on slot 0x0271549cc2…dd9eea

← previous block·next block →recent activity