← previous blocknext block →recent activity

Analyzing

Block #71,089,886

30 transactions · 27 stateful · 2026-04-28 13:31:26 UTC

Parallelism

77/100

Blocked

52%

Avg conflicts / tx

1.1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,089,886  ·  30 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xceb55b97…2612

0xd32edf…ff58

13 touches
21 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0xd113ab32…727b

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

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

21 conflicts on slot 0xceb55b9760…742612

← previous block·next block →recent activity