← previous blocknext block →recent activity

Analyzing

Block #74,216,295

10 transactions · 8 stateful · 2026-05-13 00:56:44 UTC

Parallelism

70/100

Blocked

38%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,216,295  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x1eb0fab5…3517

0x34b655…2a6f

4 touches
1 conflict

0x9c11d943…f33a

0x0555e3…2b9c

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a568

0x188d58…ea8e

2 touches
0 conflicts

0x00000000…006f

0x1efe02…37d6

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity