← previous blocknext block →recent activity

Analyzing

Block #74,516,451

19 transactions · 15 stateful · 2026-05-14 10:14:55 UTC

Parallelism

68/100

Blocked

60%

Avg conflicts / tx

1.21

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,516,451  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x22e0cc1d…ad04

0x34b655…2a6f

8 touches
6 conflicts

0xa472d565…9fe4

0x3bd359…433a

8 touches
6 conflicts

0xac2a0273…7212

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0001

0xcc67aa…c71c

6 touches
3 conflicts

0xc824469a…641c

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1539

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…401e

0x34b655…2a6f

6 touches
3 conflicts

0x00c46468…f328

0x3bd359…433a

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

6 conflicts on slot 0x22e0cc1d4a…90ad04

← previous block·next block →recent activity