← previous blocknext block →recent activity

Analyzing

Block #74,505,268

17 transactions · 8 stateful · 2026-05-14 08:59:35 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,505,268  ·  17 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

0xd6aabe89…92f5

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

2 touches
0 conflicts

0x037849a8…fa88

0x34b655…2a6f

2 touches
0 conflicts

0x037849a8…fa8d

0x34b655…2a6f

2 touches
0 conflicts

0x6c98ebd9…ca13

0x34b655…2a6f

2 touches
0 conflicts

0xea02471d…153a

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 0xd6aabe893a…bf92f5

← previous block·next block →recent activity