← previous blocknext block →recent activity

Analyzing

Block #71,289,694

31 transactions · 23 stateful · 2026-04-29 11:41:22 UTC

Parallelism

58/100

Blocked

74%

Avg conflicts / tx

2.87

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #71,289,694  ·  31 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0x2c0d0a66…103f

0xd32edf…ff58

25 touches
78 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

8 touches
6 conflicts

0xa0dd011c…ef26

0x1b6862…e19c

6 touches
3 conflicts

0xfe3bddd2…8b48

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xe3a39655…96ec

0x065c9d…c394

5 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

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

78 conflicts on slot 0x2c0d0a660c…a8103f

← previous block·next block →recent activity