← previous blocknext block →recent activity

Analyzing

Block #75,572,595

17 transactions · 15 stateful · 2026-05-19 08:00:24 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

0.71

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,572,595  ·  17 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

0x08d31c28…d50f

0x34b655…2a6f

6 touches
3 conflicts

0x0aa885fa…a3d1

0x2a68ba…90c5

6 touches
3 conflicts

0xb245fe36…d765

0x34b655…2a6f

6 touches
3 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

6 touches
3 conflicts

0xbd6348ab…8abd

0xd32edf…ff58

5 touches
3 conflicts

0x8549b75f…3a18

0x065c9d…c394

5 touches
3 conflicts

0xcb45d9d6…cb82

0x1b6862…e19c

4 touches
1 conflict

0x3b86caa0…a2a9

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 0x08d31c2849…fed50f

← previous block·next block →recent activity