← previous blocknext block →recent activity

Analyzing

Block #75,128,314

35 transactions · 30 stateful · 2026-05-17 06:24:43 UTC

Parallelism

60/100

Blocked

70%

Avg conflicts / tx

2.69

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #75,128,314  ·  35 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

18 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0xdfa45ee2…45c6

0x34b655…2a6f

16 touches
28 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x9ef7a88e…c466

0xd32edf…ff58

9 touches
10 conflicts

0xf8f1e808…a4fd

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

8 touches
6 conflicts

0x20ac0567…c954

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

36 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity