Block #70,908,806

← previous blocknext block →recent activity

Analyzing

Block #70,908,806

20 transactions · 20 stateful · 2026-04-27 17:25:33 UTC

Parallelism

75/100

Blocked

30%

Avg conflicts / tx

0.65

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,908,806  ·  20 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0002

0xb857c1…9be1

6 touches
3 conflicts

0x87a380d9…2d04

0x34b655…2a6f

6 touches
3 conflicts

0xa0f5612a…9804

0x34b655…2a6f

6 touches
3 conflicts

0xd11dc26e…59ab

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xeebd31ac…0794

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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: 0x34b6552d…112a6f

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity