← previous blocknext block →recent activity

Analyzing

Block #75,760,079

14 transactions · 10 stateful · 2026-05-20 04:50:41 UTC

Parallelism

79/100

Blocked

40%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,760,079  ·  14 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

0x422d5490…52d9

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0xcc4f1f14…aa5f

0x065c9d…c394

4 touches
1 conflict

0xdfa159d0…1576

0x065c9d…c394

4 touches
1 conflict

0xd6aabe89…92f5

0x34b655…2a6f

4 touches
1 conflict

0x97b0b2ee…4666

0x34b655…2a6f

4 touches
1 conflict

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: Perpl

3 conflicts on slot 0x422d549061…1f52d9

← previous block·next block →recent activity