← previous blocknext block →recent activity

Analyzing

Block #70,892,548

34 transactions · 31 stateful · 2026-04-27 15:37:16 UTC

Parallelism

71/100

Blocked

55%

Avg conflicts / tx

1.41

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #70,892,548  ·  34 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

8 touches
6 conflicts

0x00000000…0003

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity