← previous blocknext block →recent activity

Analyzing

Block #74,454,692

39 transactions · 30 stateful · 2026-05-14 03:22:44 UTC

Parallelism

82/100

Blocked

63%

Avg conflicts / tx

1.15

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,454,692  ·  39 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

0x00000000…0001

0xcc67aa…c71c

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

10 touches
10 conflicts

0xaa3492db…3703

0x34b655…2a6f

10 touches
10 conflicts

0xc0f25d9d…67d1

0x34b655…2a6f

10 touches
10 conflicts

0x00c46468…f328

0x3bd359…433a

10 touches
10 conflicts

0xa472d565…9fe4

0x3bd359…433a

10 touches
10 conflicts

0x44ad89ba…cf83

0x5c2513…7777

10 touches
10 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: 0xcc67aab1…cac71c

10 conflicts on slot 0x0000000000…000001

← previous block·next block →recent activity