← previous blocknext block →recent activity

Analyzing

Block #74,515,371

23 transactions · 18 stateful · 2026-05-14 10:07:40 UTC

Parallelism

74/100

Blocked

39%

Avg conflicts / tx

0.74

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,515,371  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x9fc59146…736c

0x34b655…2a6f

10 touches
10 conflicts

0x4d3e58e0…a2d7

0x34b655…2a6f

8 touches
6 conflicts

0x1c389468…6b0e

0x34b655…2a6f

8 touches
6 conflicts

0x1eb0fab5…3517

0x34b655…2a6f

8 touches
6 conflicts

0xfe20cb8f…f03d

0x34b655…2a6f

7 touches
6 conflicts

0xe181f491…f4e3

0x34b655…2a6f

6 touches
3 conflicts

0xb8228d38…3953

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity