← previous blocknext block →recent activity

Analyzing

Block #70,909,171

18 transactions · 14 stateful · 2026-04-27 17:27:59 UTC

Parallelism

83/100

Blocked

14%

Avg conflicts / tx

0.17

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,909,171  ·  18 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

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x09c32066…9cc0

0x065c9d…c394

3 touches
1 conflict

0x438cf5f6…f077

0x2a68ba…90c5

2 touches
0 conflicts

0x2af5f63a…b7b9

0x2e3234…7d90

2 touches
0 conflicts

0x02b9fc0f…34e8

0x73ada1…8be0

2 touches
0 conflicts

0x8956cb26…42f7

0x73ada1…8be0

2 touches
0 conflicts

0x8956cb26…42fa

0x73ada1…8be0

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

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity