← previous blocknext block →recent activity

Analyzing

Block #75,470,024

30 transactions · 25 stateful · 2026-05-18 20:28:33 UTC

Parallelism

80/100

Blocked

60%

Avg conflicts / tx

1.43

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #75,470,024  ·  30 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

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x54efe8d0…f3d5

0xd32edf…ff58

9 touches
10 conflicts

0xf91b744e…9117

0x754704…b603

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x1c354dc0…96de

0x754704…b603

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity