← previous blocknext block →recent activity

Analyzing

Block #74,459,174

21 transactions · 18 stateful · 2026-05-14 03:52:36 UTC

Parallelism

67/100

Blocked

39%

Avg conflicts / tx

0.86

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,459,174  ·  21 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

0x51d015d4…f911

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0000

0xfa32f9…f3f0

6 touches
3 conflicts

0x00000000…0001

0xfa32f9…f3f0

6 touches
3 conflicts

0x679795a0…a28c

0xfa32f9…f3f0

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

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

15 conflicts on slot 0x51d015d4ed…b0f911

← previous block·next block →recent activity