Block #70,909,014

← previous blocknext block →recent activity

Analyzing

Block #70,909,014

24 transactions · 22 stateful · 2026-04-27 17:26:56 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,909,014  ·  24 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

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…0000

0xc1a578…8e1a

6 touches
3 conflicts

0x00000000…0001

0xc1a578…8e1a

6 touches
3 conflicts

0x24968e6d…0132

0x131a2e…0da9

4 touches
2 conflicts

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

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: 0x2a68ba18…8e90c5

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity