← previous blocknext block →recent activity

Analyzing

Block #74,319,559

37 transactions · 25 stateful · 2026-05-13 12:23:29 UTC

Parallelism

76/100

Blocked

72%

Avg conflicts / tx

1.43

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,319,559  ·  37 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0x2c5e8e5f…769b

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x77570573…3e20

0xd32edf…ff58

7 touches
6 conflicts

0xcb45d9d6…cb81

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x20ac0567…c954

0x34b655…2a6f

6 touches
3 conflicts

0x2484cc15…5afc

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: 0x34b6552d…112a6f

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity