← previous blocknext block →recent activity

Analyzing

Block #75,478,222

27 transactions · 20 stateful · 2026-05-18 21:23:03 UTC

Parallelism

70/100

Blocked

50%

Avg conflicts / tx

1.33

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #75,478,222  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x08626d57…f094

0xd32edf…ff58

15 touches
28 conflicts

0xcb45d9d6…cb80

0x1b6862…e19c

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x873f3074…b830

0xee8c0e…1242

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

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

28 conflicts on slot 0x08626d5770…b9f094

← previous block·next block →recent activity