← previous blocknext block →recent activity

Analyzing

Block #74,762,860

34 transactions · 31 stateful · 2026-05-15 13:44:13 UTC

Parallelism

68/100

Blocked

61%

Avg conflicts / tx

1.38

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,762,860  ·  34 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x0de7749d…5bef

0x34b655…2a6f

8 touches
6 conflicts

0xbad4e90b…33a5

0x34b655…2a6f

8 touches
6 conflicts

0x9f8a2bcc…2618

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x759dccc6…a766

0x34b655…2a6f

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity