← previous blocknext block →recent activity

Analyzing

Block #74,218,377

18 transactions · 17 stateful · 2026-05-13 01:10:36 UTC

Parallelism

44/100

Blocked

65%

Avg conflicts / tx

2.94

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,218,377  ·  18 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

0x60f7fbaf…bd58

0x34b655…2a6f

18 touches
36 conflicts

0xdbc578df…706a

0x34b655…2a6f

16 touches
28 conflicts

0x664bf99e…0a8c

0x34b655…2a6f

16 touches
28 conflicts

0x2484cc15…5afc

0x34b655…2a6f

14 touches
21 conflicts

0xafd59af5…5257

0xc8689a…ee79

14 touches
21 conflicts

0x20ac0567…c954

0x34b655…2a6f

14 touches
21 conflicts

0xeb0915f1…c150

0x34b655…2a6f

14 touches
21 conflicts

0xb8e4b27f…98e3

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

36 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity