← previous blocknext block →recent activity

Analyzing

Block #74,762,108

43 transactions · 34 stateful · 2026-05-15 13:39:11 UTC

Parallelism

79/100

Blocked

65%

Avg conflicts / tx

1.86

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,762,108  ·  43 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0xfd470586…9f83

0xd32edf…ff58

17 touches
36 conflicts

0x388e001a…7e04

0x34b655…2a6f

14 touches
21 conflicts

0x0a2250a8…3cb1

0x34b655…2a6f

14 touches
21 conflicts

0x313f2565…5b00

0x34b655…2a6f

14 touches
21 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

14 touches
21 conflicts

0x9be2b99a…a959

0x34b655…2a6f

14 touches
21 conflicts

0xac8e97a0…8426

0x34b655…2a6f

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

36 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity