← previous blocknext block →recent activity

Analyzing

Block #75,297,502

22 transactions · 19 stateful · 2026-05-18 01:15:21 UTC

Parallelism

64/100

Blocked

63%

Avg conflicts / tx

1.45

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,297,502  ·  22 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

0xe54a1f6f…18f2

0x34b655…2a6f

12 touches
15 conflicts

0xf853eb8e…4027

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xd7a2b02f…1da4

0x34b655…2a6f

8 touches
6 conflicts

0x0529cc11…1d3a

0xd32edf…ff58

7 touches
6 conflicts

0x6aa624fd…a84f

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x0711ec2d…d973

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: 0x34b6552d…112a6f

15 conflicts on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity