← previous blocknext block →recent activity

Analyzing

Block #76,213,552

17 transactions · 16 stateful · 2026-05-22 07:12:25 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.65

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #76,213,552  ·  17 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

0xea57afd0…4232

0x34b655…2a6f

6 touches
3 conflicts

0x3a6e7600…e1f1

0xa6afd3…d132

6 touches
3 conflicts

0xf3d7a307…4d63

0x065c9d…c394

6 touches
3 conflicts

0xbfd1260f…f0c1

0x34b655…2a6f

6 touches
3 conflicts

0x0520da1d…c88e

0x34b655…2a6f

4 touches
1 conflict

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x3c35979a…975d

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

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 0xea57afd097…7f4232

← previous block·next block →recent activity