Block #71,683,628

← previous blocknext block →recent activity

Analyzing

Block #71,683,628

33 transactions · 21 stateful · 2026-05-01 07:29:21 UTC

Parallelism

58/100

Blocked

71%

Avg conflicts / tx

2.88

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #71,683,628  ·  33 txs across 14 waves  ·  depth 14
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

wave w13

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

0x1b186779…604e

0xd32edf…ff58

27 touches
91 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0x9256b810…52cb

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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: 0xd32edf66…9fff58

91 conflicts on slot 0x1b18677907…81604e

← previous block·next block →recent activity