← previous blocknext block →recent activity

Analyzing

Block #75,128,289

18 transactions · 16 stateful · 2026-05-17 06:24:33 UTC

Parallelism

39/100

Blocked

63%

Avg conflicts / tx

2.67

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,128,289  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

14 touches
21 conflicts

0x3e693216…fa0e

0x34b655…2a6f

12 touches
15 conflicts

0x0711ec2d…d973

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

8 touches
6 conflicts

0x9cc607d0…c9c7

0x34b655…2a6f

8 touches
6 conflicts

0xd49762c9…1359

0x34b655…2a6f

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity