← previous blocknext block →recent activity

Analyzing

Block #74,477,166

31 transactions · 25 stateful · 2026-05-14 05:52:15 UTC

Parallelism

77/100

Blocked

48%

Avg conflicts / tx

0.65

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,477,166  ·  31 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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0001

0xcc67aa…c71c

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00c46468…f328

0x3bd359…433a

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x44ad89ba…cf83

0x5c2513…7777

6 touches
3 conflicts

0xce2b6650…ecc3

0x5c2513…7777

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity