← previous blocknext block →recent activity

Analyzing

Block #74,456,427

38 transactions · 27 stateful · 2026-05-14 03:34:20 UTC

Parallelism

79/100

Blocked

59%

Avg conflicts / tx

1.26

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,456,427  ·  38 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

0xf3981be5…2c47

0x34b655…2a6f

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xeb92da41…e2ff

0xd32edf…ff58

9 touches
10 conflicts

0xe9976b58…82b8

0x34b655…2a6f

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

8 touches
6 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

8 touches
6 conflicts

0x309ef367…e8a1

0x34b655…2a6f

7 touches
6 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

28 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity