← previous blocknext block →recent activity

Analyzing

Block #74,455,484

28 transactions · 24 stateful · 2026-05-14 03:28:02 UTC

Parallelism

61/100

Blocked

67%

Avg conflicts / tx

1.57

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,455,484  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

12 touches
15 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

0xce2b6650…ecc3

0x5c2513…7777

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0000

0xcc67aa…c71c

10 touches
10 conflicts

0x00000000…0001

0xcc67aa…c71c

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: 0x34b6552d…112a6f

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity