← previous blocknext block →recent activity

Analyzing

Block #74,458,535

18 transactions · 13 stateful · 2026-05-14 03:48:21 UTC

Parallelism

83/100

Blocked

23%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,458,535  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x0de7749d…5bef

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0xd6aabe89…92f5

0x34b655…2a6f

4 touches
1 conflict

0x96f39b8e…f795

0x34b655…2a6f

4 touches
1 conflict

0x9d1b186e…3f3a

0xd32edf…ff58

3 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

2 touches
0 conflicts

0x1d3d0a53…5f57

0x065c9d…c394

2 touches
0 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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity