← previous blocknext block →recent activity

Analyzing

Block #74,338,505

11 transactions · 11 stateful · 2026-05-13 14:29:29 UTC

Parallelism

64/100

Blocked

27%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,338,505  ·  11 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x0de7749d…5bef

0x34b655…2a6f

4 touches
1 conflict

0x6a53b1c0…c3f2

0x34b655…2a6f

4 touches
1 conflict

0x7020a307…de6c

0x065c9d…c394

2 touches
0 conflicts

0x729c91b8…9537

0x188d58…ea8e

2 touches
0 conflicts

0x729c91b8…9539

0x188d58…ea8e

2 touches
0 conflicts

0x0872abbe…9c39

0x2a68ba…90c5

2 touches
0 conflicts

0x76e559a4…77fb

0x2a68ba…90c5

2 touches
0 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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity