← previous blocknext block →recent activity

Analyzing

Block #74,359,892

32 transactions · 23 stateful · 2026-05-13 16:51:39 UTC

Parallelism

78/100

Blocked

43%

Avg conflicts / tx

0.75

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,359,892  ·  32 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

12 touches
15 conflicts

0xc6417de0…2191

0xc8689a…ee79

10 touches
10 conflicts

0xaa3492db…3703

0x34b655…2a6f

10 touches
10 conflicts

0x313f2565…5b00

0x34b655…2a6f

10 touches
10 conflicts

0x23951077…539b

0x34b655…2a6f

10 touches
10 conflicts

0xaef9058e…322a

0x34b655…2a6f

10 touches
10 conflicts

0x3638e1ad…ec0e

0x34b655…2a6f

9 touches
10 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

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

15 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity