← previous blocknext block →recent activity

Analyzing

Block #74,509,078

15 transactions · 11 stateful · 2026-05-14 09:25:15 UTC

Parallelism

80/100

Blocked

18%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,509,078  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8d0e98f3…7ba0

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x33018431…8f5e

0x188d58…ea8e

2 touches
0 conflicts

0x4aa4f53b…899f

0x188d58…ea8e

2 touches
0 conflicts

0x4aa4f53b…89a1

0x188d58…ea8e

2 touches
0 conflicts

0x256918f1…c4d0

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity