← previous blocknext block →recent activity

Analyzing

Block #74,248,568

28 transactions · 23 stateful · 2026-05-13 04:31:20 UTC

Parallelism

57/100

Blocked

78%

Avg conflicts / tx

2.93

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,248,568  ·  28 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0xdc833112…155f

0xd32edf…ff58

23 touches
66 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x768cffcd…2648

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001f

0x1b6862…e19c

6 touches
3 conflicts

0xcf3283ba…c9fa

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

66 conflicts on slot 0xdc833112b9…77155f

← previous block·next block →recent activity