← previous blocknext block →recent activity

Analyzing

Block #74,491,262

32 transactions · 27 stateful · 2026-05-14 07:26:06 UTC

Parallelism

84/100

Blocked

48%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,491,262  ·  32 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0xd3b16e47…a86f

0xd32edf…ff58

7 touches
6 conflicts

0x0d2947c3…98d6

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x6dd62d2b…f17e

0x34b655…2a6f

6 touches
3 conflicts

0x4582e32d…1abe

0x34b655…2a6f

4 touches
1 conflict

0x12309510…0ac2

0x000000…012a

4 touches
1 conflict

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: 0x754704bc…afb603

6 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity