← previous blocknext block →recent activity

Analyzing

Block #74,428,599

17 transactions · 11 stateful · 2026-05-14 00:28:59 UTC

Parallelism

82/100

Blocked

18%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,428,599  ·  17 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

0xbad68552…e6bf

0x34b655…2a6f

4 touches
1 conflict

0xbb12db23…857e

0x34b655…2a6f

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6e

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e70

0x188d58…ea8e

2 touches
0 conflicts

0xcb8c97d5…6338

0x188d58…ea8e

2 touches
0 conflicts

0xcb8c97d5…6339

0x188d58…ea8e

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