← previous blocknext block →recent activity

Analyzing

Block #74,351,972

32 transactions · 27 stateful · 2026-05-13 15:58:56 UTC

Parallelism

59/100

Blocked

67%

Avg conflicts / tx

1.78

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #74,351,972  ·  32 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x66acfc31…45de

0xd32edf…ff58

17 touches
36 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21c0

0x1b6862…e19c

8 touches
6 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

36 conflicts on slot 0x66acfc3169…6a45de

← previous block·next block →recent activity