← previous blocknext block →recent activity

Analyzing

Block #71,089,802

38 transactions · 35 stateful · 2026-04-28 13:30:52 UTC

Parallelism

76/100

Blocked

54%

Avg conflicts / tx

1.47

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,089,802  ·  38 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xaa5bf1a7…3bab

0xd32edf…ff58

11 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x1c913164…5c2e

0x34b655…2a6f

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x17c8d049…52aa

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity