← previous blocknext block →recent activity

Analyzing

Block #75,139,593

13 transactions · 11 stateful · 2026-05-17 07:39:52 UTC

Parallelism

77/100

Blocked

18%

Avg conflicts / tx

0.15

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,139,593  ·  13 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

0x1b061426…38a2

0x34b655…2a6f

4 touches
1 conflict

0xe54a1f6f…18f2

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x005fb969…2d97

0x34b655…2a6f

2 touches
0 conflicts

0x0711ec2d…d973

0x34b655…2a6f

2 touches
0 conflicts

0x2965e2d6…5800

0x34b655…2a6f

2 touches
0 conflicts

0x62d6e82b…a750

0x34b655…2a6f

2 touches
0 conflicts

0x631b4113…baa9

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: 0x34b6552d…112a6f

1 conflict on slot 0x1b061426bc…8c38a2

← previous block·next block →recent activity