← previous blocknext block →recent activity

Analyzing

Block #75,478,668

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

Parallelism

63/100

Blocked

66%

Avg conflicts / tx

2.86

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #75,478,668  ·  35 txs across 13 waves  ·  depth 13
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

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

0x42585cce…41c0

0xd32edf…ff58

25 touches
78 conflicts

0xee0a9ebb…c425

0x0555e3…2b9c

8 touches
6 conflicts

0x00000000…0000

0x094452…0a09

8 touches
6 conflicts

0x00000000…0004

0x094452…0a09

8 touches
6 conflicts

0x9e223b01…38b2

0x3bd359…433a

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x4039b31f…0f4a

0x754704…b603

8 touches
6 conflicts

0x5dfa485c…cf52

0x754704…b603

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 0x42585cce48…8241c0

← previous block·next block →recent activity