← previous blocknext block →recent activity

Analyzing

Block #74,951,915

22 transactions · 20 stateful · 2026-05-16 10:46:17 UTC

Parallelism

55/100

Blocked

55%

Avg conflicts / tx

2

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,951,915  ·  22 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

0xe54a1f6f…18f2

0x34b655…2a6f

18 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0xc6417de0…2191

0xc8689a…ee79

12 touches
15 conflicts

0x0711ec2d…d973

0x34b655…2a6f

12 touches
15 conflicts

0x45b9e08c…a11b

0x34b655…2a6f

12 touches
15 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

12 touches
15 conflicts

0xd49762c9…1359

0x34b655…2a6f

12 touches
15 conflicts

0xa5bfbb45…1ee8

0x34b655…2a6f

10 touches
10 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

36 conflicts on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity