← previous blocknext block →recent activity

Analyzing

Block #74,647,145

10 transactions · 7 stateful · 2026-05-15 00:51:35 UTC

Parallelism

70/100

Blocked

29%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,647,145  ·  10 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

0xd11dc26e…59ab

0x34b655…2a6f

4 touches
1 conflict

0xfefd1e1d…5fed

0x34b655…2a6f

4 touches
1 conflict

0xb0a4e112…f855

0x34b655…2a6f

4 touches
1 conflict

0x309ef367…e8a1

0x34b655…2a6f

2 touches
0 conflicts

0x3faefef6…621c

0x34b655…2a6f

2 touches
0 conflicts

0x482471ad…122f

0x34b655…2a6f

2 touches
0 conflicts

0x53b4ef2b…8a05

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