← previous blocknext block →recent activity

Analyzing

Block #74,765,285

23 transactions · 19 stateful · 2026-05-15 14:00:25 UTC

Parallelism

70/100

Blocked

58%

Avg conflicts / tx

0.96

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,765,285  ·  23 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

0x58a97abe…7b94

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

8 touches
6 conflicts

0x6aa624fd…a84d

0x1b6862…e19c

8 touches
6 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

8 touches
6 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

10 conflicts on slot 0x58a97abed5…597b94

← previous block·next block →recent activity