← previous blocknext block →recent activity

Analyzing

Block #74,335,822

42 transactions · 32 stateful · 2026-05-13 14:11:35 UTC

Parallelism

76/100

Blocked

66%

Avg conflicts / tx

1.79

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,335,822  ·  42 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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xf3981be5…2c47

0x34b655…2a6f

12 touches
15 conflicts

0x73ac9cf8…7be6

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

8 touches
6 conflicts

0x93afca4c…b479

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity