← previous blocknext block →recent activity

Analyzing

Block #74,293,879

22 transactions · 19 stateful · 2026-05-13 09:32:39 UTC

Parallelism

41/100

Blocked

63%

Avg conflicts / tx

3.36

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #74,293,879  ·  22 txs across 13 waves  ·  depth 13
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

wave w12

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

0x60f7fbaf…bd58

0x34b655…2a6f

22 touches
55 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

22 touches
55 conflicts

0xa80253b7…135e

0x34b655…2a6f

20 touches
45 conflicts

0xa009aa7b…a5ba

0x34b655…2a6f

20 touches
45 conflicts

0xc6417de0…2191

0xc8689a…ee79

20 touches
45 conflicts

0x5d70606a…1d53

0x34b655…2a6f

20 touches
45 conflicts

0x9be2b99a…a959

0x34b655…2a6f

20 touches
45 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

20 touches
45 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

55 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity