← previous blocknext block →recent activity

Analyzing

Block #74,671,428

28 transactions · 25 stateful · 2026-05-15 03:33:47 UTC

Parallelism

75/100

Blocked

60%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,671,428  ·  28 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xaf567ef5…1a30

0xd32edf…ff58

13 touches
21 conflicts

0x8a35acfb…d1a9

0x8d66a4…3095

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

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

21 conflicts on slot 0xaf567ef573…6e1a30

← previous block·next block →recent activity