← previous blocknext block →recent activity

Analyzing

Block #74,241,030

32 transactions · 25 stateful · 2026-05-13 03:41:11 UTC

Parallelism

72/100

Blocked

68%

Avg conflicts / tx

1.44

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,241,030  ·  32 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

14 touches
21 conflicts

0x772b830f…2ae4

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 conflicts

0x93afca4c…b47f

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001f

0x1b6862…e19c

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

21 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity