← previous blocknext block →recent activity

Analyzing

Block #74,562,628

14 transactions · 10 stateful · 2026-05-14 15:26:35 UTC

Parallelism

79/100

Blocked

20%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,562,628  ·  14 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

0xd6d040d9…9ae3

0x34b655…2a6f

4 touches
1 conflict

0xcab72563…329a

0x34b655…2a6f

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

2 touches
0 conflicts

0x1348a4c0…8d18

0x34b655…2a6f

2 touches
0 conflicts

0x1348a4c0…8d19

0x34b655…2a6f

2 touches
0 conflicts

0x1e9bb30c…e78e

0x34b655…2a6f

2 touches
0 conflicts

0x310a7246…2dcb

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity