← previous blocknext block →recent activity

Analyzing

Block #75,103,162

13 transactions · 11 stateful · 2026-05-17 03:36:49 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,103,162  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x631b4113…baa9

0x34b655…2a6f

4 touches
1 conflict

0xf90ba4b4…6fa0

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x11f25e19…8bb1

0x34b655…2a6f

2 touches
0 conflicts

0x62d6e82b…a750

0x34b655…2a6f

2 touches
0 conflicts

0x9b36f19f…fa5a

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 0x631b41138f…31baa9

← previous block·next block →recent activity