← previous blocknext block →recent activity

Analyzing

Block #75,123,289

29 transactions · 21 stateful · 2026-05-17 05:51:13 UTC

Parallelism

79/100

Blocked

57%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,123,289  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x46c4719d…16bc

0xd32edf…ff58

7 touches
6 conflicts

0x9dccd2a9…2790

0x34b655…2a6f

6 touches
3 conflicts

0xc7f28b7a…5777

0x34b655…2a6f

6 touches
3 conflicts

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x388f889f…a655

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity