← previous blocknext block →recent activity

Analyzing

Block #74,456,911

27 transactions · 17 stateful · 2026-05-14 03:37:33 UTC

Parallelism

78/100

Blocked

53%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,456,911  ·  27 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

0x815d4da5…d8db

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x5cfec795…7c0e

0x34b655…2a6f

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0xc03a03cd…fbcf

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

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: 0xd32edf66…9fff58

10 conflicts on slot 0x815d4da572…b6d8db

← previous block·next block →recent activity