← previous blocknext block →recent activity

Analyzing

Block #74,234,246

20 transactions · 16 stateful · 2026-05-13 02:56:06 UTC

Parallelism

65/100

Blocked

56%

Avg conflicts / tx

1.4

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,234,246  ·  20 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x9ef83c66…4437

0x34b655…2a6f

10 touches
10 conflicts

0x5de96bd3…c60c

0x34b655…2a6f

10 touches
10 conflicts

0x30d572a8…a787

0x34b655…2a6f

8 touches
6 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

8 touches
6 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x8a85cf3d…2868

0x34b655…2a6f

8 touches
6 conflicts

0x908d4442…2c4b

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

10 conflicts on slot 0x9ef83c6614…2e4437

← previous block·next block →recent activity