← previous blocknext block →recent activity

Analyzing

Block #71,416,581

37 transactions · 26 stateful · 2026-04-30 01:47:19 UTC

Parallelism

76/100

Blocked

77%

Avg conflicts / tx

1.62

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,416,581  ·  37 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x5332bee9…0c38

0xd32edf…ff58

17 touches
36 conflicts

0x676f9f01…a8ac

0x34b655…2a6f

10 touches
10 conflicts

0x78694995…f66e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0x1a49b049…a7f4

0x065c9d…c394

7 touches
6 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

36 conflicts on slot 0x5332bee94d…d10c38

← previous block·next block →recent activity