← previous blocknext block →recent activity

Analyzing

Block #74,765,317

38 transactions · 28 stateful · 2026-05-15 14:00:38 UTC

Parallelism

60/100

Blocked

71%

Avg conflicts / tx

1.92

Longest chain

15 deep

Execution timeline

did this block parallelize well?

view

block #74,765,317  ·  38 txs across 15 waves  ·  depth 15
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

wave w13

wave w14

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

16 touches
28 conflicts

0x388e001a…7e04

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xd1efa4d1…de24

0xd32edf…ff58

7 touches
6 conflicts

0x57de3828…3fbb

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

6 touches
3 conflicts

0x9be2b99a…a959

0x34b655…2a6f

6 touches
3 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

28 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity