← previous blocknext block →recent activity

Analyzing

Block #74,510,738

19 transactions · 10 stateful · 2026-05-14 09:36:28 UTC

Parallelism

84/100

Blocked

20%

Avg conflicts / tx

0.16

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,510,738  ·  19 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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x1dc86774…166a

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xc03a03cd…fbcf

0x34b655…2a6f

3 touches
1 conflict

0x9b8800c1…ed12

0x34b655…2a6f

3 touches
1 conflict

0x1dd25224…7cef

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 0xac2a02739b…81721b

← previous block·next block →recent activity