← previous blocknext block →recent activity

Analyzing

Block #70,891,665

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

Parallelism

82/100

Blocked

48%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,891,665  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x1fc5b588…4ff0

0xee8c0e…1242

10 touches
10 conflicts

0xf45ff565…e32f

0x754704…b603

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

4 touches
1 conflict

0x6b1259e6…4e11

0x1b6862…e19c

4 touches
1 conflict

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: 0xee8c0e9f…481242

10 conflicts on slot 0x1fc5b58885…844ff0

← previous block·next block →recent activity