← previous blocknext block →recent activity

Analyzing

Block #74,915,044

22 transactions · 20 stateful · 2026-05-16 06:39:39 UTC

Parallelism

77/100

Blocked

55%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,915,044  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf5d7a59e…e77f

0xd32edf…ff58

7 touches
6 conflicts

0xf3d7a307…4d63

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xea57afd0…4232

0x34b655…2a6f

6 touches
3 conflicts

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x8f6d4bd6…4e51

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: 0xd32edf66…9fff58

6 conflicts on slot 0xf5d7a59ec3…c1e77f

← previous block·next block →recent activity