← previous blocknext block →recent activity

Analyzing

Block #74,353,116

35 transactions · 29 stateful · 2026-05-13 16:06:33 UTC

Parallelism

74/100

Blocked

55%

Avg conflicts / tx

1.4

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,353,116  ·  35 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x80ba87bb…88b5

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0xba5743c7…21c0

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x801a6e57…d85c

0x34b655…2a6f

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity