← previous blocknext block →recent activity

Analyzing

Block #70,957,048

30 transactions · 28 stateful · 2026-04-27 22:46:43 UTC

Parallelism

87/100

Blocked

54%

Avg conflicts / tx

0.8

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,957,048  ·  30 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xbbee74c2…567a

0x065c9d…c394

8 touches
6 conflicts

0x00000000…0002

0xb857c1…9be1

8 touches
6 conflicts

0x00000000…0001

0x8fd63a…536c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0000

0x8fd63a…536c

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

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: 0x065c9d28…a9c394

6 conflicts on slot 0xbbee74c2e7…6e567a

← previous block·next block →recent activity