← previous blocknext block →recent activity

Analyzing

Block #74,786,969

35 transactions · 27 stateful · 2026-05-15 16:25:29 UTC

Parallelism

66/100

Blocked

63%

Avg conflicts / tx

1.69

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,786,969  ·  35 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

0xd98b3c10…67b8

0x34b655…2a6f

18 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd77fe603…e5eb

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x0a2250a8…3cb1

0x34b655…2a6f

6 touches
3 conflicts

0x388e001a…7e04

0x34b655…2a6f

6 touches
3 conflicts

0x5dc14a96…6816

0x34b655…2a6f

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: 0x34b6552d…112a6f

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity