← previous blocknext block →recent activity

Analyzing

Block #74,771,623

48 transactions · 22 stateful · 2026-05-15 14:42:56 UTC

Parallelism

85/100

Blocked

59%

Avg conflicts / tx

0.71

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,771,623  ·  48 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

0x60f7fbaf…bd58

0x34b655…2a6f

14 touches
21 conflicts

0x0d03bddb…6658

0x34b655…2a6f

10 touches
10 conflicts

0xc6d2c861…9c7c

0x34b655…2a6f

8 touches
6 conflicts

0x10814d14…cdda

0x34b655…2a6f

8 touches
6 conflicts

0xa9988419…9f45

0x34b655…2a6f

8 touches
6 conflicts

0x9fca0d29…07dc

0x34b655…2a6f

8 touches
6 conflicts

0x86cea35b…bdff

0x34b655…2a6f

8 touches
6 conflicts

0x374426df…f445

0xc8689a…ee79

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: 0x34b6552d…112a6f

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity