← previous blocknext block →recent activity

Analyzing

Block #74,284,154

28 transactions · 25 stateful · 2026-05-13 08:27:52 UTC

Parallelism

68/100

Blocked

68%

Avg conflicts / tx

2.18

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,284,154  ·  28 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

0xc5713161…92ad

0xd32edf…ff58

17 touches
36 conflicts

0xb9d2cf20…a668

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0x928d6b23…536d

0x1b6862…e19c

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: 0xd32edf66…9fff58

36 conflicts on slot 0xc5713161c1…5b92ad

← previous block·next block →recent activity