← previous blocknext block →recent activity

Analyzing

Block #74,920,407

47 transactions · 32 stateful · 2026-05-16 07:15:30 UTC

Parallelism

81/100

Blocked

59%

Avg conflicts / tx

1.3

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,920,407  ·  47 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xcb714855…d298

0xd32edf…ff58

15 touches
28 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x2bbc0cfb…c2c0

0x1b6862…e19c

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xd9f18d9a…141d

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

28 conflicts on slot 0xcb7148553a…78d298

← previous block·next block →recent activity