← previous blocknext block →recent activity

Analyzing

Block #75,478,226

40 transactions · 25 stateful · 2026-05-18 21:23:05 UTC

Parallelism

63/100

Blocked

76%

Avg conflicts / tx

2.55

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #75,478,226  ·  40 txs across 15 waves  ·  depth 15
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

wave w12

wave w13

wave w14

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

0x74c9ecb3…0ad8

0xd32edf…ff58

25 touches
78 conflicts

0x17606ba6…1b6e

0x754704…b603

14 touches
21 conflicts

0xe75ce681…ba5f

0x188d58…ea8e

14 touches
21 conflicts

0xe75ce681…ba61

0x188d58…ea8e

12 touches
15 conflicts

0x0dbf9688…c6cf

0xd18b7e…414b

10 touches
10 conflicts

0x792299c4…16b1

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

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

78 conflicts on slot 0x74c9ecb319…4e0ad8

← previous block·next block →recent activity