← previous blocknext block →recent activity

Analyzing

Block #74,223,576

10 transactions · 8 stateful · 2026-05-13 01:45:11 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,223,576  ·  10 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x10814d14…cdda

0x34b655…2a6f

4 touches
1 conflict

0xa9988419…9f45

0x34b655…2a6f

4 touches
1 conflict

0x1df07d43…ff95

0x34b655…2a6f

2 touches
0 conflicts

0x25d14f47…d664

0x34b655…2a6f

2 touches
0 conflicts

0x405c35c6…473b

0x34b655…2a6f

2 touches
0 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

2 touches
0 conflicts

0x4ec9ff52…e6f7

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

1 conflict on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity