← previous blocknext block →recent activity

Analyzing

Block #71,289,692

37 transactions · 25 stateful · 2026-04-29 11:41:21 UTC

Parallelism

65/100

Blocked

60%

Avg conflicts / tx

1.89

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #71,289,692  ·  37 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

0x92d09582…8ed8

0xd32edf…ff58

21 touches
55 conflicts

0xac79a0c7…be13

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0013

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

14 touches
21 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0x00000000…001c

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 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

55 conflicts on slot 0x92d09582dd…ad8ed8

← previous block·next block →recent activity