← previous blocknext block →recent activity

Analyzing

Block #70,891,718

16 transactions · 13 stateful · 2026-04-27 15:31:44 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,891,718  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x8956cb26…42fa

0x73ada1…8be0

6 touches
3 conflicts

0xf4e554ca…1a6c

0x73ada1…8be0

6 touches
3 conflicts

0x1b4df54f…7afb

0x754704…b603

6 touches
3 conflicts

0xa3dc6f35…13e9

0x754704…b603

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x7b7bcac3…8fbf

0x34b655…2a6f

4 touches
1 conflict

0x7f323e7f…db8a

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

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: 0x73ada1ea…808be0

3 conflicts on slot 0x8956cb2667…8342fa

← previous block·next block →recent activity