← previous blocknext block →recent activity

Analyzing

Block #74,764,994

41 transactions · 29 stateful · 2026-05-15 13:58:28 UTC

Parallelism

78/100

Blocked

59%

Avg conflicts / tx

1.27

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,764,994  ·  41 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

0x83e0fe09…f9a0

0xd32edf…ff58

17 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

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

36 conflicts on slot 0x83e0fe0988…6bf9a0

← previous block·next block →recent activity