Block #70,908,587

← previous blocknext block →recent activity

Analyzing

Block #70,908,587

37 transactions · 33 stateful · 2026-04-27 17:24:06 UTC

Parallelism

81/100

Blocked

55%

Avg conflicts / tx

1.27

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,908,587  ·  37 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…0002

0xb857c1…9be1

14 touches
21 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0x3ff344f5…30bf

0x34b655…2a6f

4 touches
1 conflict

0xe6bc2705…d15b

0x34b655…2a6f

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: 0xb857c13a…1a9be1

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity