← previous blocknext block →recent activity

Analyzing

Block #74,284,377

15 transactions · 12 stateful · 2026-05-13 08:29:22 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,284,377  ·  15 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

0xb9d2cf20…a668

0x34b655…2a6f

4 touches
1 conflict

0x1eb0fab5…3517

0x34b655…2a6f

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x2f2ad1b4…d9f3

0xd32edf…ff58

3 touches
1 conflict

0x3e38d1a2…4b35

0x065c9d…c394

2 touches
0 conflicts

0x7243b794…4405

0x065c9d…c394

2 touches
0 conflicts

0xa2963f12…e85a

0x065c9d…c394

2 touches
0 conflicts

0xcf3283ba…c9fa

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

1 conflict on slot 0xb9d2cf2005…28a668

← previous block·next block →recent activity