← previous blocknext block →recent activity

Analyzing

Block #75,105,193

28 transactions · 21 stateful · 2026-05-17 03:50:24 UTC

Parallelism

82/100

Blocked

57%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,105,193  ·  28 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

0x7aece196…5944

0xd32edf…ff58

7 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x0711ec2d…d973

0x34b655…2a6f

4 touches
1 conflict

0x41a10fb4…e4e1

0x34b655…2a6f

4 touches
1 conflict

0x6eba5e7f…4b52

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 0x7aece196a7…445944

← previous block·next block →recent activity