← previous blocknext block →recent activity

Analyzing

Block #75,476,889

17 transactions · 15 stateful · 2026-05-18 21:14:11 UTC

Parallelism

76/100

Blocked

33%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #75,476,889  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x5f77d607…2c84

0x065c9d…c394

6 touches
3 conflicts

0x26a6faee…aa49

0x34b655…2a6f

4 touches
1 conflict

0x5648d337…a780

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xdeaa385f…6b8b

0x34b655…2a6f

4 touches
1 conflict

0xdf352747…7eaf

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity