← previous blocknext block →recent activity

Analyzing

Block #74,389,337

17 transactions · 16 stateful · 2026-05-13 20:07:41 UTC

Parallelism

53/100

Blocked

56%

Avg conflicts / tx

1.82

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,389,337  ·  17 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

0x1c389468…6b0e

0x34b655…2a6f

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xea02471d…1542

0x34b655…2a6f

14 touches
21 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

10 touches
10 conflicts

0xf3d10975…0d07

0x34b655…2a6f

10 touches
10 conflicts

0xa678cb89…4abd

0x34b655…2a6f

7 touches
6 conflicts

0x8cc18498…ce7e

0x34b655…2a6f

7 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

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 0x1c38946843…a16b0e

← previous block·next block →recent activity