← previous blocknext block →recent activity

Analyzing

Block #71,089,730

27 transactions · 22 stateful · 2026-04-28 13:30:23 UTC

Parallelism

59/100

Blocked

55%

Avg conflicts / tx

1.59

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #71,089,730  ·  27 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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0x4381471a…9ac1

0x34b655…2a6f

8 touches
6 conflicts

0xc1f28224…cb43

0x34b655…2a6f

8 touches
6 conflicts

0x75f6889e…7f1e

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xb96e29a5…0419

0x34b655…2a6f

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: 0x34b6552d…112a6f

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity