← previous blocknext block →recent activity

Analyzing

Block #74,920,264

22 transactions · 17 stateful · 2026-05-16 07:14:32 UTC

Parallelism

59/100

Blocked

59%

Avg conflicts / tx

1.59

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,920,264  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x388e001a…7e04

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x9be2b99a…a959

0x34b655…2a6f

12 touches
15 conflicts

0xaa3492db…3703

0x34b655…2a6f

12 touches
15 conflicts

0x68728b15…33fc

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

12 touches
15 conflicts

0xaef9058e…322a

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

21 conflicts on slot 0x388e001a16…e57e04

← previous block·next block →recent activity