← previous blocknext block →recent activity

Analyzing

Block #74,352,475

27 transactions · 21 stateful · 2026-05-13 16:02:17 UTC

Parallelism

81/100

Blocked

48%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,352,475  ·  27 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

0x0e080fb1…8287

0xd32edf…ff58

7 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0x6b319071…a105

0xc8689a…ee79

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

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

6 conflicts on slot 0x0e080fb141…278287

← previous block·next block →recent activity