← previous blocknext block →recent activity

Analyzing

Block #74,761,120

28 transactions · 24 stateful · 2026-05-15 13:32:31 UTC

Parallelism

64/100

Blocked

63%

Avg conflicts / tx

1.82

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,761,120  ·  28 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xc6417de0…2191

0xc8689a…ee79

18 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0x5d70606a…1d53

0x34b655…2a6f

14 touches
21 conflicts

0x9be2b99a…a959

0x34b655…2a6f

14 touches
21 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

14 touches
21 conflicts

0xa009aa7b…a5ba

0x34b655…2a6f

14 touches
21 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

12 touches
15 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: 0xc8689a47…62ee79

36 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity