← previous blocknext block →recent activity

Analyzing

Block #75,079,118

12 transactions · 11 stateful · 2026-05-17 00:56:19 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,079,118  ·  12 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

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x90b41ae4…e1d7

0x065c9d…c394

3 touches
1 conflict

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0xeda2edc3…91d8

0x000000…012a

2 touches
0 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

2 touches
0 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

2 touches
0 conflicts

0x4aa4f53b…899f

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: 0x754704bc…afb603

1 conflict on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity