← previous blocknext block →recent activity

Analyzing

Block #75,478,686

30 transactions · 18 stateful · 2026-05-18 21:26:12 UTC

Parallelism

60/100

Blocked

72%

Avg conflicts / tx

1.6

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #75,478,686  ·  30 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x17606ba6…1b6e

0x754704…b603

14 touches
21 conflicts

0x1b7d88d0…35db

0xd32edf…ff58

11 touches
15 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

10 touches
10 conflicts

0x969f2d28…4fa2

0x0555e3…2b9c

8 touches
6 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

8 touches
6 conflicts

0xe75ce681…ba61

0x188d58…ea8e

8 touches
6 conflicts

0xe92fd8b2…882a

0xd18b7e…414b

8 touches
6 conflicts

0x00000000…0002

0xd2634e…53b1

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: 0x754704bc…afb603

21 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity