← previous blocknext block →recent activity

Analyzing

Block #75,427,094

15 transactions · 13 stateful · 2026-05-18 15:42:46 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,427,094  ·  15 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x892daf6e…48d8

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0x537b38ff…2c21

0x34b655…2a6f

4 touches
1 conflict

0x74e485b1…d380

0x34b655…2a6f

4 touches
1 conflict

0x10d80fee…dbda

0x1d1325…2305

2 touches
0 conflicts

0x3484c9df…bfd5

0x1d1325…2305

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity