← previous blocknext block →recent activity

Analyzing

Block #75,591,357

16 transactions · 14 stateful · 2026-05-19 10:05:21 UTC

Parallelism

81/100

Blocked

29%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,591,357  ·  16 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

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x17cd1479…00bb

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a8

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a9

0x8d66a4…3095

5 touches
3 conflicts

0x15698ac9…2a46

0x34b655…2a6f

4 touches
1 conflict

0x3a9149df…72e0

0x34b655…2a6f

4 touches
1 conflict

0x99f080dc…58c1

0x34b655…2a6f

4 touches
1 conflict

0xc2d4d818…7182

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity