← previous blocknext block →recent activity

Analyzing

Block #75,195,840

14 transactions · 10 stateful · 2026-05-17 13:55:32 UTC

Parallelism

79/100

Blocked

30%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,195,840  ·  14 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

0x83f3d320…fb59

0x34b655…2a6f

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x9dccd2a9…2790

0x34b655…2a6f

4 touches
1 conflict

0xbaeed020…92f8

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe2a6ee72…96b3

0x34b655…2a6f

4 touches
1 conflict

0x4d889c10…e6b2

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

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

3 conflicts on slot 0x83f3d32000…25fb59

← previous block·next block →recent activity