← previous blocknext block →recent activity

Analyzing

Block #74,332,279

40 transactions · 32 stateful · 2026-05-13 13:48:01 UTC

Parallelism

80/100

Blocked

63%

Avg conflicts / tx

1.07

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,332,279  ·  40 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0xa90e52fe…7eb1

0x34b655…2a6f

10 touches
10 conflicts

0xcf87d565…146d

0xd32edf…ff58

9 touches
10 conflicts

0x1c389468…6b0e

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0xaa3492db…3703

0x34b655…2a6f

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

10 conflicts on slot 0x62d080e928…5a4a7c

← previous block·next block →recent activity