← previous blocknext block →recent activity

Analyzing

Block #74,352,234

42 transactions · 28 stateful · 2026-05-13 16:00:40 UTC

Parallelism

71/100

Blocked

68%

Avg conflicts / tx

1.38

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,352,234  ·  42 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

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x374426df…f445

0xc8689a…ee79

8 touches
6 conflicts

0x908d4442…2c4b

0x34b655…2a6f

8 touches
6 conflicts

0x95e5ee51…5e3e

0x34b655…2a6f

8 touches
6 conflicts

0xa54d4519…267f

0x34b655…2a6f

8 touches
6 conflicts

0xa9988419…9f45

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity