← previous blocknext block →recent activity

Analyzing

Block #75,097,994

20 transactions · 18 stateful · 2026-05-17 03:02:21 UTC

Parallelism

60/100

Blocked

67%

Avg conflicts / tx

1.75

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,097,994  ·  20 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

0x99a3a7c1…1e2b

0x0cc9b2…7777

16 touches
28 conflicts

0xa472d565…9fe4

0x3bd359…433a

16 touches
28 conflicts

0xa10c86f8…4b74

0x3bd359…433a

16 touches
28 conflicts

0x00000000…0000

0x019883…2a9a

16 touches
28 conflicts

0x00000000…0002

0x019883…2a9a

16 touches
28 conflicts

0x44ad89ba…cf83

0x0cc9b2…7777

16 touches
28 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

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: 0x0cc9b2e2…2e7777

28 conflicts on slot 0x99a3a7c17c…081e2b

← previous block·next block →recent activity