← previous blocknext block →recent activity

Analyzing

Block #75,591,658

11 transactions · 8 stateful · 2026-05-19 10:07:21 UTC

Parallelism

82/100

Blocked

25%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,591,658  ·  11 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

0xba56c5b2…8040

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x0aa885fa…a3d1

0x2a68ba…90c5

4 touches
1 conflict

0x9976b928…3d5f

0xd32edf…ff58

3 touches
1 conflict

0x969f2d28…4fa2

0x0555e3…2b9c

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x46cb45de…a566

0x188d58…ea8e

2 touches
0 conflicts

0x46cb45de…a568

0x188d58…ea8e

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: 0x065c9d28…a9c394

1 conflict on slot 0xba56c5b26d…c98040

← previous block·next block →recent activity