← previous blocknext block →recent activity

Analyzing

Block #75,096,312

28 transactions · 20 stateful · 2026-05-17 02:51:07 UTC

Parallelism

61/100

Blocked

60%

Avg conflicts / tx

1.89

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,096,312  ·  28 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

0xe54a1f6f…18f2

0x34b655…2a6f

20 touches
45 conflicts

0xf853eb8e…4027

0x34b655…2a6f

20 touches
45 conflicts

0x7cbd466f…1700

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x001aafdc…6f07

0x34b655…2a6f

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0x0711ec2d…d973

0x34b655…2a6f

10 touches
10 conflicts

0x55b6a001…1e7a

0x34b655…2a6f

10 touches
10 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

45 conflicts on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity