← previous blocknext block →recent activity

Analyzing

Block #75,845,876

22 transactions · 15 stateful · 2026-05-20 14:23:03 UTC

Parallelism

77/100

Blocked

53%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,845,876  ·  22 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x451e482b…7e7d

0x34b655…2a6f

6 touches
3 conflicts

0x892daf6e…48d8

0x065c9d…c394

4 touches
1 conflict

0x99a21305…dffc

0x2a68ba…90c5

4 touches
1 conflict

0x1c63f4ce…bf2c

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 touches
1 conflict

0x5c7bd5d6…6ab7

0x34b655…2a6f

4 touches
1 conflict

0x904fc3c0…00ec

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity