← previous blocknext block →recent activity

Analyzing

Block #75,732,978

32 transactions · 22 stateful · 2026-05-20 01:50:23 UTC

Parallelism

75/100

Blocked

59%

Avg conflicts / tx

1.16

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,732,978  ·  32 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x20646043…0f78

0xd32edf…ff58

15 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xb7b446d2…2006

0x34b655…2a6f

6 touches
3 conflicts

0x625a0267…4ad6

0x34b655…2a6f

4 touches
1 conflict

0x70f62910…9c41

0x34b655…2a6f

4 touches
1 conflict

0xa3ff1ab2…8ae3

0x34b655…2a6f

4 touches
1 conflict

0xaa0d0542…d8ec

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…7212

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

28 conflicts on slot 0x20646043a9…a90f78

← previous block·next block →recent activity