← previous blocknext block →recent activity

Analyzing

Block #75,262,390

13 transactions · 11 stateful · 2026-05-17 21:20:14 UTC

Parallelism

69/100

Blocked

27%

Avg conflicts / tx

0.46

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,262,390  ·  13 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

0x9fc6ea79…e2dc

0x34b655…2a6f

8 touches
6 conflicts

0x35b65947…44d1

0xc8689a…ee79

4 touches
1 conflict

0x90687d94…b524

0x34b655…2a6f

4 touches
1 conflict

0x90e14f35…24e2

0x34b655…2a6f

4 touches
1 conflict

0xa9988419…9f45

0x34b655…2a6f

4 touches
1 conflict

0xba9f88e8…9c33

0x34b655…2a6f

4 touches
1 conflict

0xd32f8498…be67

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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 0x9fc6ea791d…ace2dc

← previous block·next block →recent activity