← previous blocknext block →recent activity

Analyzing

Block #74,336,788

33 transactions · 23 stateful · 2026-05-13 14:18:01 UTC

Parallelism

79/100

Blocked

57%

Avg conflicts / tx

1.15

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,336,788  ·  33 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0x374426df…f445

0xc8689a…ee79

6 touches
3 conflicts

0x20b94f7c…2a9b

0x34b655…2a6f

6 touches
3 conflicts

0x10814d14…cdda

0x34b655…2a6f

6 touches
3 conflicts

0x728f999a…832f

0x34b655…2a6f

6 touches
3 conflicts

0xa9988419…9f45

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