← previous blocknext block →recent activity

Analyzing

Block #70,891,682

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

Parallelism

90/100

Blocked

54%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,891,682  ·  40 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

0xe6455d1f…1029

0x754704…b603

8 touches
6 conflicts

0x0d0b2509…074d

0x3bd359…433a

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x79410e66…4087

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0002

0x659bd0…a9da

6 touches
3 conflicts

0x7e28e55c…d05c

0x754704…b603

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xcce2fd99…a8eb

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: 0x754704bc…afb603

6 conflicts on slot 0xe6455d1fbe…eb1029

← previous block·next block →recent activity