← previous blocknext block →recent activity

Analyzing

Block #71,244,642

29 transactions · 19 stateful · 2026-04-29 06:41:33 UTC

Parallelism

62/100

Blocked

63%

Avg conflicts / tx

2.03

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #71,244,642  ·  29 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xc5710046…842e

0xd32edf…ff58

21 touches
55 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x01e7b865…6e6d

0x188d58…ea8e

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

6 touches
3 conflicts

0x11998eac…f9a2

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002b

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

55 conflicts on slot 0xc5710046a3…f0842e

← previous block·next block →recent activity