← previous blocknext block →recent activity

Analyzing

Block #74,774,697

32 transactions · 27 stateful · 2026-05-15 15:03:30 UTC

Parallelism

63/100

Blocked

78%

Avg conflicts / tx

2.34

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,774,697  ·  32 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

0x60f7fbaf…bd58

0x34b655…2a6f

20 touches
45 conflicts

0x388e001a…7e04

0x34b655…2a6f

14 touches
21 conflicts

0xc6417de0…2191

0xc8689a…ee79

12 touches
15 conflicts

0x9be2b99a…a959

0x34b655…2a6f

12 touches
15 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

12 touches
15 conflicts

0xf70f4aef…dafa

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

10 touches
10 conflicts

0x161e1ca1…0fd7

0x34b655…2a6f

10 touches
10 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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity