Block #70,878,221

← previous blocknext block →recent activity

Analyzing

Block #70,878,221

20 transactions · 17 stateful · 2026-04-27 14:01:56 UTC

Parallelism

75/100

Blocked

41%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,878,221  ·  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

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x8a35acfb…d1b0

0x8d66a4…3095

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ae

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1af

0x8d66a4…3095

6 touches
3 conflicts

0x904fc3c0…00ec

0x34b655…2a6f

6 touches
3 conflicts

0x7f430e47…4cbd

0x8d66a4…3095

6 touches
3 conflicts

0x9be2b99a…a959

0x34b655…2a6f

6 touches
3 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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity