← previous blocknext block →recent activity

Analyzing

Block #75,732,981

39 transactions · 31 stateful · 2026-05-20 01:50:25 UTC

Parallelism

72/100

Blocked

71%

Avg conflicts / tx

2.05

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,732,981  ·  39 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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…0013

0x1b6862…e19c

16 touches
28 conflicts

0x17a7f697…dcb6

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

16 touches
28 conflicts

0xe86a37b8…b1b7

0xd32edf…ff58

15 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0012

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…001d

0x1b6862…e19c

14 touches
21 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

28 conflicts on slot 0x0000000000…000013

← previous block·next block →recent activity