← previous blocknext block →recent activity

Analyzing

Block #74,344,351

23 transactions · 19 stateful · 2026-05-13 15:08:19 UTC

Parallelism

61/100

Blocked

58%

Avg conflicts / tx

1.22

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,344,351  ·  23 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xcc8b6d32…6601

0x34b655…2a6f

7 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x2225e639…a10e

0x34b655…2a6f

6 touches
3 conflicts

0xb409e204…89ac

0x34b655…2a6f

6 touches
3 conflicts

0x247cfb80…cca8

0x34b655…2a6f

6 touches
3 conflicts

0xf3981be5…2c47

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity