← previous blocknext block →recent activity

Analyzing

Block #74,359,783

23 transactions · 19 stateful · 2026-05-13 16:50:55 UTC

Parallelism

70/100

Blocked

58%

Avg conflicts / tx

1.57

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,359,783  ·  23 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

0xa472d565…9fe4

0x3bd359…433a

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x5675c293…17d9

0x34b655…2a6f

8 touches
6 conflicts

0xc3aacf13…6b3d

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

8 touches
6 conflicts

0x0b28bf77…e53a

0x34b655…2a6f

6 touches
3 conflicts

0x55b6a001…1e7a

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: 0x3bd359c1…15433a

21 conflicts on slot 0xa472d565a0…ae9fe4

← previous block·next block →recent activity