← previous blocknext block →recent activity

Analyzing

Block #74,284,568

22 transactions · 17 stateful · 2026-05-13 08:30:38 UTC

Parallelism

55/100

Blocked

59%

Avg conflicts / tx

2

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,284,568  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

14 touches
21 conflicts

0x56a064ab…6c7d

0x34b655…2a6f

10 touches
10 conflicts

0x57de3828…3fbb

0x34b655…2a6f

6 touches
3 conflicts

0x5d70606a…1d53

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x6c44331f…9735

0x34b655…2a6f

6 touches
3 conflicts

0x7cbd466f…1700

0x34b655…2a6f

6 touches
3 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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity