← previous blocknext block →recent activity

Analyzing

Block #74,252,327

33 transactions · 29 stateful · 2026-05-13 04:56:16 UTC

Parallelism

67/100

Blocked

79%

Avg conflicts / tx

2.64

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,252,327  ·  33 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

0xc27346d4…90a3

0x9c82eb…cd90

18 touches
36 conflicts

0x00000000…0036

0x293e2f…13a7

18 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x81e1f4e8…08d7

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x318ac0bb…6b9c

0x34b655…2a6f

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: 0x9c82eb49…c6cd90

36 conflicts on slot 0xc27346d4a3…bb90a3

← previous block·next block →recent activity