← previous blocknext block →recent activity

Analyzing

Block #74,795,838

12 transactions · 10 stateful · 2026-05-15 17:24:43 UTC

Parallelism

83/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,795,838  ·  12 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

0xb138d087…4689

0x34b655…2a6f

4 touches
1 conflict

0xd5ad0af4…2387

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x02d2adff…e661

0x065c9d…c394

2 touches
0 conflicts

0x2746a602…e1fc

0x065c9d…c394

2 touches
0 conflicts

0x34b75579…8e4c

0x065c9d…c394

2 touches
0 conflicts

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0x7503becd…afcb

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 0xb138d08737…2b4689

← previous block·next block →recent activity