← previous blocknext block →recent activity

Analyzing

Block #74,735,154

18 transactions · 11 stateful · 2026-05-15 10:38:57 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.22

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,735,154  ·  18 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x9fc6ea79…e2dc

0x34b655…2a6f

4 touches
1 conflict

0xfe2bac2b…2cec

0x065c9d…c394

4 touches
1 conflict

0x1e5c3e35…3d38

0x065c9d…c394

3 touches
1 conflict

0xb0190fbc…81ed

0x065c9d…c394

3 touches
1 conflict

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 conflicts

0x23114fac…630a

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity