← previous blocknext block →recent activity

Analyzing

Block #74,240,604

14 transactions · 13 stateful · 2026-05-13 03:38:21 UTC

Parallelism

43/100

Blocked

62%

Avg conflicts / tx

2.07

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,240,604  ·  14 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x5de96bd3…c60c

0x34b655…2a6f

14 touches
21 conflicts

0x2f387761…308c

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

10 touches
10 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x23951077…539b

0x34b655…2a6f

8 touches
6 conflicts

0x32ee90db…decc

0x34b655…2a6f

8 touches
6 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 0x5de96bd34a…ecc60c

← previous block·next block →recent activity