← previous blocknext block →recent activity

Analyzing

Block #74,353,751

35 transactions · 25 stateful · 2026-05-13 16:10:47 UTC

Parallelism

74/100

Blocked

60%

Avg conflicts / tx

1.34

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,353,751  ·  35 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

10 touches
10 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

10 touches
10 conflicts

0x0d622e34…0000

0x681e90…ae09

8 touches
6 conflicts

0xa54d4519…267f

0x34b655…2a6f

8 touches
6 conflicts

0x0711ec2d…d973

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity