← previous blocknext block →recent activity

Analyzing

Block #70,951,995

15 transactions · 13 stateful · 2026-04-27 22:13:04 UTC

Parallelism

80/100

Blocked

31%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,951,995  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…0001

0x8fd63a…536c

6 touches
3 conflicts

0x00000000…0000

0x8fd63a…536c

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0000

0xc1a578…8e1a

4 touches
1 conflict

0x00000000…0001

0xc1a578…8e1a

4 touches
1 conflict

0x05e5ce66…b69d

0x2880ab…7b43

2 touches
0 conflicts

0x0cfb5d79…7ccb

0x2880ab…7b43

2 touches
0 conflicts

0x0cfb5d79…7ccc

0x2880ab…7b43

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: 0x8fd63afb…2f536c

3 conflicts on slot 0x0000000000…000001

← previous block·next block →recent activity