← previous blocknext block →recent activity

Analyzing

Block #75,129,541

17 transactions · 16 stateful · 2026-05-17 06:32:55 UTC

Parallelism

82/100

Blocked

31%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,129,541  ·  17 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

0x7ca7baa7…d46d

0x34b655…2a6f

6 touches
3 conflicts

0x7cee1be1…e770

0x34b655…2a6f

6 touches
3 conflicts

0x3e49348b…9445

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x765c236f…ff45

0x2a68ba…90c5

4 touches
1 conflict

0x2965e2d6…5800

0x34b655…2a6f

4 touches
1 conflict

0x41d3bfa5…523e

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

3 conflicts on slot 0x7ca7baa7f4…7bd46d

← previous block·next block →recent activity