← previous blocknext block →recent activity

Analyzing

Block #74,601,925

23 transactions · 21 stateful · 2026-05-14 19:50:06 UTC

Parallelism

78/100

Blocked

48%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,601,925  ·  23 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x24968e6d…0132

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

6 touches
3 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

6 touches
3 conflicts

0xbad68552…e6bf

0x34b655…2a6f

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity