← previous blocknext block →recent activity

Analyzing

Block #74,334,209

16 transactions · 13 stateful · 2026-05-13 14:00:54 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,334,209  ·  16 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

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x14244448…ccb5

0x34b655…2a6f

2 touches
0 conflicts

0x4b4ba403…c3d1

0x34b655…2a6f

2 touches
0 conflicts

0x52f2f7aa…0dc9

0x34b655…2a6f

2 touches
0 conflicts

0x5603cb7c…1c48

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: 0xab35264b…1cfa38

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity