← previous blocknext block →recent activity

Analyzing

Block #70,845,809

21 transactions · 15 stateful · 2026-04-27 10:26:00 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

0.81

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,845,809  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0x03924cd3…f268

0x8d66a4…3095

7 touches
6 conflicts

0x7f430e47…4cbd

0x8d66a4…3095

6 touches
3 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…0004

0x8d66a4…3095

6 touches
3 conflicts

0x8aa1941d…2988

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1aa

0x8d66a4…3095

5 touches
3 conflicts

0x8a35acfb…d1ab

0x8d66a4…3095

5 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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity