← previous blocknext block →recent activity

Analyzing

Block #75,478,696

35 transactions · 15 stateful · 2026-05-18 21:26:16 UTC

Parallelism

80/100

Blocked

67%

Avg conflicts / tx

0.86

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #75,478,696  ·  35 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x57b251d8…c902

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x5dfa485c…cf52

0x754704…b603

6 touches
3 conflicts

0x00000000…0000

0x9b60e5…f8ac

6 touches
3 conflicts

0x00000000…0002

0x9b60e5…f8ac

6 touches
3 conflicts

0xee0a9ebb…c425

0x0555e3…2b9c

6 touches
3 conflicts

0xe75ce681…ba61

0x188d58…ea8e

6 touches
3 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

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

21 conflicts on slot 0x57b251d8ab…b4c902

← previous block·next block →recent activity