← previous blocknext block →recent activity

Analyzing

Block #74,510,635

24 transactions · 13 stateful · 2026-05-14 09:35:46 UTC

Parallelism

83/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,510,635  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xfe20cb8f…f03d

0x34b655…2a6f

5 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

0x34b655…2a6f

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0x8d0e98f3…7ba0

0x34b655…2a6f

4 touches
1 conflict

0x1eb0fab5…3517

0x34b655…2a6f

4 touches
1 conflict

0x78067279…d187

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity