← previous blocknext block →recent activity

Analyzing

Block #75,847,180

22 transactions · 16 stateful · 2026-05-20 14:31:47 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,847,180  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x80b0653d…5706

0x34b655…2a6f

6 touches
3 conflicts

0x792299c4…16b8

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0004

0x8d66a4…3095

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xdb6c434f…6cb1

0xd32edf…ff58

5 touches
3 conflicts

0x17cd1479…00bb

0x8d66a4…3095

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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity