← previous blocknext block →recent activity

Analyzing

Block #75,732,662

28 transactions · 21 stateful · 2026-05-20 01:48:18 UTC

Parallelism

79/100

Blocked

57%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,732,662  ·  28 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

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x37d49489…9309

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x91220b8f…7a06

0x1b6862…e19c

8 touches
6 conflicts

0xe2a31c42…bc66

0xd32edf…ff58

7 touches
6 conflicts

0x0aa885fa…a3d1

0x2a68ba…90c5

6 touches
3 conflicts

0xaa3492db…3703

0x34b655…2a6f

6 touches
3 conflicts

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: 0x1b68626d…2de19c

6 conflicts on slot 0x0000000000…000015

← previous block·next block →recent activity