← previous blocknext block →recent activity

Analyzing

Block #74,774,696

34 transactions · 21 stateful · 2026-05-15 15:03:30 UTC

Parallelism

76/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,774,696  ·  34 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x388e001a…7e04

0x34b655…2a6f

16 touches
28 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

10 touches
10 conflicts

0x9be2b99a…a959

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x161e1ca1…0fd7

0x34b655…2a6f

8 touches
6 conflicts

0x65b89141…61de

0x34b655…2a6f

8 touches
6 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

28 conflicts on slot 0x388e001a16…e57e04

← previous block·next block →recent activity