← previous blocknext block →recent activity

Analyzing

Block #70,891,709

38 transactions · 31 stateful · 2026-04-27 15:31:40 UTC

Parallelism

79/100

Blocked

52%

Avg conflicts / tx

1.24

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #70,891,709  ·  38 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x3c98feee…0796

0xd32edf…ff58

13 touches
21 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

8 touches
6 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0x6b1259e6…4e11

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

21 conflicts on slot 0x3c98feee83…200796

← previous block·next block →recent activity