← previous blocknext block →recent activity

Analyzing

Block #74,332,277

37 transactions · 26 stateful · 2026-05-13 13:48:01 UTC

Parallelism

70/100

Blocked

62%

Avg conflicts / tx

1.41

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,332,277  ·  37 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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

8 touches
6 conflicts

0x525b3d52…ade3

0x34b655…2a6f

8 touches
6 conflicts

0x154490c6…3760

0xd32edf…ff58

7 touches
6 conflicts

0x99f080dc…58c1

0x34b655…2a6f

6 touches
3 conflicts

0x0711ec2d…d973

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity