← previous blocknext block →recent activity

Analyzing

Block #74,461,956

11 transactions · 6 stateful · 2026-05-14 04:11:06 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,461,956  ·  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

0xeb0915f1…c150

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

2 touches
0 conflicts

0x2acc1b4e…92a5

0x34b655…2a6f

2 touches
0 conflicts

0x4582e32d…1abe

0x34b655…2a6f

2 touches
0 conflicts

0x5cfec795…7c0e

0x34b655…2a6f

2 touches
0 conflicts

0x7cb2f3fa…4836

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