← previous blocknext block →recent activity

Analyzing

Block #74,555,896

28 transactions · 23 stateful · 2026-05-14 14:40:58 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,555,896  ·  28 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x62d080e9…4a7c

0x34b655…2a6f

14 touches
21 conflicts

0xd6e02140…b2b5

0x34b655…2a6f

10 touches
10 conflicts

0xc3aacf13…6b3d

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x313f2565…5b00

0x34b655…2a6f

6 touches
3 conflicts

0x52aeabb0…482b

0x34b655…2a6f

6 touches
3 conflicts

0x7cbd466f…1700

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 0x62d080e928…5a4a7c

← previous block·next block →recent activity