← previous blocknext block →recent activity

Analyzing

Block #75,515,661

28 transactions · 20 stateful · 2026-05-19 01:39:51 UTC

Parallelism

79/100

Blocked

55%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,515,661  ·  28 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

0x5f77d607…2c84

0x065c9d…c394

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x5086c64a…28ba

0x34b655…2a6f

8 touches
6 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

6 touches
3 conflicts

0x9e719c7a…df63

0x34b655…2a6f

6 touches
3 conflicts

0x892daf6e…48d8

0x065c9d…c394

6 touches
3 conflicts

0x083a8763…5a79

0x1b6862…e19c

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: 0x065c9d28…a9c394

6 conflicts on slot 0x5f77d60791…b12c84

← previous block·next block →recent activity