← previous blocknext block →recent activity

Analyzing

Block #75,079,114

39 transactions · 36 stateful · 2026-05-17 00:56:17 UTC

Parallelism

74/100

Blocked

67%

Avg conflicts / tx

2

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #75,079,114  ·  39 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x903d7988…effd

0xd32edf…ff58

15 touches
28 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x00000000…0028

0x1b6862…e19c

8 touches
6 conflicts

0xc3483764…f296

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

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

28 conflicts on slot 0x903d79880a…18effd

← previous block·next block →recent activity