← previous blocknext block →recent activity

Analyzing

Block #74,586,089

7 transactions · 6 stateful · 2026-05-14 18:03:47 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,586,089  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x7b6d2deb…dde0

0x34b655…2a6f

4 touches
1 conflict

0xca0fef1c…b548

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

2 touches
0 conflicts

0x1eb0fab5…3517

0x34b655…2a6f

2 touches
0 conflicts

0x8e66c393…c9a2

0x34b655…2a6f

2 touches
0 conflicts

0xc56d6548…50a4

0x34b655…2a6f

2 touches
0 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

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

1 conflict on slot 0x7b6d2debd6…b6dde0

← previous block·next block →recent activity