← previous blocknext block →recent activity

Analyzing

Block #74,606,560

33 transactions · 26 stateful · 2026-05-14 20:21:07 UTC

Parallelism

64/100

Blocked

65%

Avg conflicts / tx

1.94

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,606,560  ·  33 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

0xa91c899f…6ee3

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0x42446806…33dd

0x34b655…2a6f

10 touches
10 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x57de3828…3fbb

0x34b655…2a6f

8 touches
6 conflicts

0xd49762c9…1359

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