← previous blocknext block →recent activity

Analyzing

Block #74,555,948

29 transactions · 24 stateful · 2026-05-14 14:41:19 UTC

Parallelism

69/100

Blocked

42%

Avg conflicts / tx

1.03

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,555,948  ·  29 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

0x540ad8d2…295f

0xd32edf…ff58

13 touches
21 conflicts

0x00000000…001e

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf3d7a307…4d63

0x065c9d…c394

6 touches
3 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 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 0x540ad8d20a…cb295f

← previous block·next block →recent activity