← previous blocknext block →recent activity

Analyzing

Block #74,779,228

30 transactions · 20 stateful · 2026-05-15 15:33:49 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.53

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,779,228  ·  30 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x711053dd…6293

0xd32edf…ff58

19 touches
45 conflicts

0x14d1bf0e…e09b

0x1b6862…e19c

8 touches
6 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001a

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

45 conflicts on slot 0x711053dd2f…6a6293

← previous block·next block →recent activity