← previous blocknext block →recent activity

Analyzing

Block #75,506,403

13 transactions · 12 stateful · 2026-05-19 00:36:24 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.54

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #75,506,403  ·  13 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

0x676f9f01…a8ac

0x34b655…2a6f

6 touches
3 conflicts

0x815d8c62…b05f

0xd32edf…ff58

5 touches
3 conflicts

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x88a68e08…ff61

0x065c9d…c394

4 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb81

0x1b6862…e19c

4 touches
1 conflict

0x414e9446…4b59

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 0x676f9f01ee…dea8ac

← previous block·next block →recent activity