← previous blocknext block →recent activity

Analyzing

Block #74,555,803

31 transactions · 17 stateful · 2026-05-14 14:40:20 UTC

Parallelism

84/100

Blocked

53%

Avg conflicts / tx

0.52

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,555,803  ·  31 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf3d7a307…4d63

0x065c9d…c394

8 touches
6 conflicts

0x4b4b9e46…8b40

0xd32edf…ff58

7 touches
6 conflicts

0xba5743c7…21c5

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x801a6e57…d85c

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x99f666e3…b2a2

0x3bd359…433a

4 touches
1 conflict

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: 0x065c9d28…a9c394

6 conflicts on slot 0xf3d7a307cc…f14d63

← previous block·next block →recent activity