← previous blocknext block →recent activity

Analyzing

Block #74,190,720

19 transactions · 15 stateful · 2026-05-12 22:06:36 UTC

Parallelism

37/100

Blocked

73%

Avg conflicts / tx

2.89

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,190,720  ·  19 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

0x5de96bd3…c60c

0x34b655…2a6f

20 touches
45 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

16 touches
28 conflicts

0x2d975111…5f52

0x34b655…2a6f

16 touches
28 conflicts

0xf853eb8e…4027

0x34b655…2a6f

16 touches
28 conflicts

0xaef9058e…322a

0x34b655…2a6f

14 touches
21 conflicts

0xaa3492db…3703

0x34b655…2a6f

14 touches
21 conflicts

0x0c52cabc…caba

0x34b655…2a6f

14 touches
21 conflicts

0xc6417de0…2191

0xc8689a…ee79

14 touches
21 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

45 conflicts on slot 0x5de96bd34a…ecc60c

← previous block·next block →recent activity