← previous blocknext block →recent activity

Analyzing

Block #74,389,720

11 transactions · 9 stateful · 2026-05-13 20:10:12 UTC

Parallelism

73/100

Blocked

44%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,389,720  ·  11 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x1e8e485d…ced9

0x34b655…2a6f

2 touches
0 conflicts

0x25fd71f9…906b

0x34b655…2a6f

2 touches
0 conflicts

0x2fad73a1…ae09

0x34b655…2a6f

2 touches
0 conflicts

0x482471ad…122f

0x34b655…2a6f

2 touches
0 conflicts

0x664bf99e…0a8c

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity