Block #70,911,438

← previous blocknext block →recent activity

Analyzing

Block #70,911,438

14 transactions · 12 stateful · 2026-04-27 17:43:05 UTC

Parallelism

71/100

Blocked

25%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,911,438  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x63ba2f5a…4a0e

0xd32edf…ff58

7 touches
6 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

4 touches
1 conflict

0x5df32adf…e24a

0x065c9d…c394

3 touches
1 conflict

0x18aed20c…48f3

0x000000…012a

2 touches
0 conflicts

0x4245e4e8…096e

0x000000…012a

2 touches
0 conflicts

0x7c403af1…31b1

0x3bd359…433a

2 touches
0 conflicts

0xa23619a7…40e4

0x3bd359…433a

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

2 touches
0 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: 0xd32edf66…9fff58

6 conflicts on slot 0x63ba2f5a75…634a0e

← previous block·next block →recent activity