← previous blocknext block →recent activity

Analyzing

Block #74,310,540

32 transactions · 25 stateful · 2026-05-13 11:23:30 UTC

Parallelism

78/100

Blocked

60%

Avg conflicts / tx

1.28

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,310,540  ·  32 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

0xdd5b5fe6…c59f

0xd32edf…ff58

13 touches
21 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

12 touches
15 conflicts

0xf2e7bb96…1a54

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0012

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

21 conflicts on slot 0xdd5b5fe690…87c59f

← previous block·next block →recent activity