← previous blocknext block →recent activity

Analyzing

Block #75,297,564

24 transactions · 20 stateful · 2026-05-18 01:15:46 UTC

Parallelism

79/100

Blocked

45%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #75,297,564  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf4c9aeeb…6576

0xd32edf…ff58

9 touches
10 conflicts

0x9394e22c…3da3

0x34b655…2a6f

6 touches
3 conflicts

0xe22455da…1ce1

0x34b655…2a6f

5 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xda6b535e…6d6b

0x1b6862…e19c

4 touches
1 conflict

0x21d22421…0b7a

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: 0xd32edf66…9fff58

10 conflicts on slot 0xf4c9aeeb48…9b6576

← previous block·next block →recent activity