← previous blocknext block →recent activity

Analyzing

Block #73,920,935

26 transactions · 24 stateful · 2026-05-11 16:09:11 UTC

Parallelism

58/100

Blocked

67%

Avg conflicts / tx

2.38

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,920,935  ·  26 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x7ab7836d…af86

0xd32edf…ff58

19 touches
45 conflicts

0x765c236f…ff45

0x2a68ba…90c5

8 touches
6 conflicts

0x03df3a18…58e7

0x34b655…2a6f

8 touches
6 conflicts

0x4f483049…3cc7

0x34b655…2a6f

8 touches
6 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0xee230b20…5a0f

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

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

45 conflicts on slot 0x7ab7836d75…d7af86

← previous block·next block →recent activity