← previous blocknext block →recent activity

Analyzing

Block #76,112,011

19 transactions · 15 stateful · 2026-05-21 19:56:21 UTC

Parallelism

74/100

Blocked

53%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #76,112,011  ·  19 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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xa472d565…9fe4

0x3bd359…433a

6 touches
3 conflicts

0x13227dab…484e

0x34b655…2a6f

6 touches
3 conflicts

0xdb067026…9eb8

0x1d1325…2305

4 touches
1 conflict

0xe2263bea…6a9d

0x1d1325…2305

4 touches
1 conflict

0xe2263bea…6a9e

0x1d1325…2305

4 touches
1 conflict

0xe2263bea…6aa0

0x1d1325…2305

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