← previous blocknext block →recent activity

Analyzing

Block #75,479,157

20 transactions · 14 stateful · 2026-05-18 21:29:28 UTC

Parallelism

85/100

Blocked

14%

Avg conflicts / tx

0.15

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,479,157  ·  20 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

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x0aa885fa…a3d1

0x2a68ba…90c5

4 touches
1 conflict

0x32e62e4c…384e

0x065c9d…c394

4 touches
1 conflict

0xad436b12…f632

0x1111b3…4111

2 touches
0 conflicts

0xb3eae1cb…7249

0x1111b3…4111

2 touches
0 conflicts

0xe2e94dfa…5026

0x2a68ba…90c5

2 touches
0 conflicts

0xb7fefa89…54dc

0x754704…b603

2 touches
0 conflicts

0xffe004da…e2f4

0x754704…b603

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

3 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity