← previous blocknext block →recent activity

Analyzing

Block #70,911,663

18 transactions · 17 stateful · 2026-04-27 17:44:35 UTC

Parallelism

83/100

Blocked

24%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,911,663  ·  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

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x489cb750…7069

0x131a2e…0da9

4 touches
1 conflict

0x24968e6d…0132

0x131a2e…0da9

4 touches
1 conflict

0xcf5fc236…5ffb

0xd32edf…ff58

3 touches
1 conflict

0xc3c8642a…7da5

0x2a68ba…90c5

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

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity