← previous blocknext block →recent activity

Analyzing

Block #70,909,135

7 transactions · 6 stateful · 2026-04-27 17:27:44 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,909,135  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x28f424d9…4435

0x065c9d…c394

4 touches
1 conflict

0xf6ee2b14…b5df

0x065c9d…c394

3 touches
1 conflict

0x70364203…726a

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x9f48be7e…0030

0x065c9d…c394

2 touches
0 conflicts

0xdf9f745e…f340

0x065c9d…c394

2 touches
0 conflicts

0xf9ec9203…b6a2

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

0x131a2e…0da9

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: 0x065c9d28…a9c394

1 conflict on slot 0x28f424d9f8…a04435

← previous block·next block →recent activity