← previous blocknext block →recent activity

Analyzing

Block #74,896,339

16 transactions · 15 stateful · 2026-05-16 04:34:55 UTC

Parallelism

69/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,896,339  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x313f2565…5b00

0x34b655…2a6f

10 touches
10 conflicts

0x388e001a…7e04

0x34b655…2a6f

10 touches
10 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

10 touches
10 conflicts

0x9cc607d0…c9c7

0x34b655…2a6f

10 touches
10 conflicts

0xaa3492db…3703

0x34b655…2a6f

10 touches
10 conflicts

0xaef9058e…322a

0x34b655…2a6f

10 touches
10 conflicts

0xd49762c9…1359

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

10 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity