← previous blocknext block →recent activity

Analyzing

Block #75,517,081

20 transactions · 16 stateful · 2026-05-19 01:49:31 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,517,081  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xcab04955…5398

0xd32edf…ff58

9 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5b6af007…0f35

0x34b655…2a6f

4 touches
1 conflict

0x615bc8cc…15d2

0x34b655…2a6f

4 touches
1 conflict

0x678143da…dc6b

0x34b655…2a6f

4 touches
1 conflict

0x7151b1ad…4520

0x34b655…2a6f

4 touches
1 conflict

0x810a3aa2…0227

0x34b655…2a6f

4 touches
1 conflict

0xd30a4208…3cd2

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: 0xd32edf66…9fff58

10 conflicts on slot 0xcab04955bd…6d5398

← previous block·next block →recent activity