← previous blocknext block →recent activity

Analyzing

Block #74,765,397

38 transactions · 27 stateful · 2026-05-15 14:01:11 UTC

Parallelism

71/100

Blocked

63%

Avg conflicts / tx

1.45

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,765,397  ·  38 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x388e001a…7e04

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xe6b07966…fb8a

0xd32edf…ff58

9 touches
10 conflicts

0x9b0235a2…a1dc

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0x9256b810…52c9

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

21 conflicts on slot 0x388e001a16…e57e04

← previous block·next block →recent activity