← previous blocknext block →recent activity

Analyzing

Block #73,751,534

26 transactions · 20 stateful · 2026-05-10 21:16:16 UTC

Parallelism

58/100

Blocked

55%

Avg conflicts / tx

1.77

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,751,534  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

18 touches
36 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

10 touches
10 conflicts

0x129ba946…48ab

0x34b655…2a6f

8 touches
6 conflicts

0xedb848fe…6534

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002d

0x1b6862…e19c

4 touches
1 conflict

0x3af0dd8e…0026

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

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: 0x34b6552d…112a6f

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity