Block #70,845,833

← previous blocknext block →recent activity

Analyzing

Block #70,845,833

23 transactions · 20 stateful · 2026-04-27 10:26:10 UTC

Parallelism

52/100

Blocked

50%

Avg conflicts / tx

2.17

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #70,845,833  ·  23 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xe54a1f6f…18f2

0x34b655…2a6f

18 touches
36 conflicts

0xa7c45762…dc01

0x34b655…2a6f

16 touches
28 conflicts

0x1319ae2c…7f9a

0x34b655…2a6f

12 touches
15 conflicts

0x23951077…539b

0x34b655…2a6f

12 touches
15 conflicts

0x313f2565…5b00

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

12 touches
15 conflicts

0x908d4442…2c4b

0x34b655…2a6f

12 touches
15 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

36 conflicts on slot 0xe54a1f6fdd…7918f2

← previous block·next block →recent activity