← previous blocknext block →recent activity

Analyzing

Block #74,369,607

16 transactions · 13 stateful · 2026-05-13 17:56:17 UTC

Parallelism

56/100

Blocked

46%

Avg conflicts / tx

1.31

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,369,607  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x62d080e9…4a7c

0x34b655…2a6f

14 touches
21 conflicts

0xf10e4ac5…2f88

0x34b655…2a6f

12 touches
15 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x9be2b99a…a959

0x34b655…2a6f

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

21 conflicts on slot 0x62d080e928…5a4a7c

← previous block·next block →recent activity