← previous blocknext block →recent activity

Analyzing

Block #74,456,189

40 transactions · 25 stateful · 2026-05-14 03:32:44 UTC

Parallelism

77/100

Blocked

68%

Avg conflicts / tx

1.35

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,456,189  ·  40 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

0x5298bb9e…a34c

0xd32edf…ff58

17 touches
36 conflicts

0xf3981be5…2c47

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…002c

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…001c

0x1b6862…e19c

8 touches
6 conflicts

0x69017fce…85bf

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 0x5298bb9edc…e7a34c

← previous block·next block →recent activity