← previous blocknext block →recent activity

Analyzing

Block #74,406,613

27 transactions · 18 stateful · 2026-05-13 22:02:43 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

1.07

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,406,613  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x62d080e9…4a7c

0x34b655…2a6f

16 touches
28 conflicts

0x1c348b58…836a

0x34b655…2a6f

12 touches
15 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

10 touches
10 conflicts

0xd49762c9…1359

0x34b655…2a6f

10 touches
10 conflicts

0x050a4348…907a

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x0711ec2d…d973

0x34b655…2a6f

10 touches
10 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 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 0x62d080e928…5a4a7c

← previous block·next block →recent activity