← previous blocknext block →recent activity

Analyzing

Block #71,089,817

40 transactions · 32 stateful · 2026-04-28 13:30:58 UTC

Parallelism

80/100

Blocked

53%

Avg conflicts / tx

1.02

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #71,089,817  ·  40 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

10 touches
10 conflicts

0x17c8d049…52aa

0x34b655…2a6f

10 touches
10 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x1c913164…5c2e

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xb857c1…9be1

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x801a6e57…d85c

0x34b655…2a6f

6 touches
3 conflicts

0x9cc607d0…c9c7

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity