← previous blocknext block →recent activity

Analyzing

Block #74,204,659

34 transactions · 27 stateful · 2026-05-12 23:39:20 UTC

Parallelism

65/100

Blocked

74%

Avg conflicts / tx

2.88

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,204,659  ·  34 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x83954c5d…bf05

0xd32edf…ff58

23 touches
66 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002e

0x1b6862…e19c

6 touches
3 conflicts

0x17a7f697…dcb7

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

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

66 conflicts on slot 0x83954c5d68…c0bf05

← previous block·next block →recent activity