← previous blocknext block →recent activity

Analyzing

Block #74,796,532

13 transactions · 12 stateful · 2026-05-15 17:29:21 UTC

Parallelism

54/100

Blocked

42%

Avg conflicts / tx

1.15

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,796,532  ·  13 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x7cbd466f…1700

0x34b655…2a6f

10 touches
10 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

10 touches
10 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x313f2565…5b00

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x10814d14…cdda

0x34b655…2a6f

8 touches
6 conflicts

0x1319ae2c…7f9a

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

10 conflicts on slot 0x7cbd466f36…791700

← previous block·next block →recent activity