← previous blocknext block →recent activity

Analyzing

Block #74,510,157

17 transactions · 14 stateful · 2026-05-14 09:32:32 UTC

Parallelism

65/100

Blocked

57%

Avg conflicts / tx

1.24

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,510,157  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x2c41ab11…0210

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xac79a0c7…be14

0x1b6862…e19c

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xd11dc26e…59ab

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity