← previous blocknext block →recent activity

Analyzing

Block #74,352,690

20 transactions · 14 stateful · 2026-05-13 16:03:43 UTC

Parallelism

85/100

Blocked

29%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,352,690  ·  20 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

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x9c841608…4149

0xd32edf…ff58

3 touches
1 conflict

0x47b807a2…3307

0x065c9d…c394

2 touches
0 conflicts

0x4a5640ed…e054

0x065c9d…c394

2 touches
0 conflicts

0x66a083b4…a17a

0x065c9d…c394

2 touches
0 conflicts

0xab702642…a597

0x065c9d…c394

2 touches
0 conflicts

0xaebc3b9d…d57e

0x065c9d…c394

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