← previous blocknext block →recent activity

Analyzing

Block #70,955,816

11 transactions · 11 stateful · 2026-04-27 22:38:31 UTC

Parallelism

64/100

Blocked

27%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,955,816  ·  11 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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x24968e6d…0132

0x131a2e…0da9

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0xb7cbb23c…9a52

0x1efe02…37d6

2 touches
0 conflicts

0xce5ba70b…565a

0x1efe02…37d6

2 touches
0 conflicts

0xeb1d3b01…df98

0x1efe02…37d6

2 touches
0 conflicts

0x00000000…0099

0xaa3145…feec

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity