← previous blocknext block →recent activity

Analyzing

Block #71,094,369

37 transactions · 32 stateful · 2026-04-28 14:01:17 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

1.05

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #71,094,369  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x801a6e57…d85c

0x34b655…2a6f

8 touches
6 conflicts

0x3702b140…97ea

0x34b655…2a6f

6 touches
3 conflicts

0x3e1f7818…2fc8

0x34b655…2a6f

6 touches
3 conflicts

0x4e01a6b9…ed8e

0x34b655…2a6f

6 touches
3 conflicts

0x62d6e82b…a750

0x34b655…2a6f

6 touches
3 conflicts

0x8aa1941d…2988

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity