← previous blocknext block →recent activity

Analyzing

Block #74,457,145

24 transactions · 19 stateful · 2026-05-14 03:39:07 UTC

Parallelism

67/100

Blocked

53%

Avg conflicts / tx

1.17

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,457,145  ·  24 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x1c389468…6b0e

0x34b655…2a6f

10 touches
10 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

0x34b655…2a6f

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x111f72de…b33c

0x34b655…2a6f

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity