← previous blocknext block →recent activity

Analyzing

Block #74,352,145

29 transactions · 18 stateful · 2026-05-13 16:00:05 UTC

Parallelism

83/100

Blocked

61%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,352,145  ·  29 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x30276c1c…47b4

0x2a68ba…90c5

8 touches
6 conflicts

0x62508e18…473b

0x065c9d…c394

7 touches
6 conflicts

0xac33ff75…077b

0xfa32f9…f3f0

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0x99f666e3…b2a2

0x3bd359…433a

6 touches
3 conflicts

0x9194f4a3…10b8

0x754704…b603

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

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

6 conflicts on slot 0x30276c1c08…7247b4

← previous block·next block →recent activity