← previous blocknext block →recent activity

Analyzing

Block #70,956,964

17 transactions · 17 stateful · 2026-04-27 22:46:10 UTC

Parallelism

53/100

Blocked

53%

Avg conflicts / tx

2.29

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #70,956,964  ·  17 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x24968e6d…0132

0x065c9d…c394

8 touches
6 conflicts

0x24968e6d…0132

0x131a2e…0da9

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x45c2059a…4160

0x065c9d…c394

4 touches
1 conflict

0x5c48536d…a387

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

28 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity