← previous blocknext block →recent activity

Analyzing

Block #75,032,634

21 transactions · 16 stateful · 2026-05-16 19:46:23 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,032,634  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x765c236f…ff45

0x2a68ba…90c5

8 touches
6 conflicts

0x72226bb8…7544

0x065c9d…c394

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x3e49348b…9445

0x34b655…2a6f

4 touches
1 conflict

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x9fff6336…d849

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0003

0x63e48b…53f2

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

10 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity