← previous blocknext block →recent activity

Analyzing

Block #70,997,031

8 transactions · 6 stateful · 2026-04-28 03:13:09 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,997,031  ·  8 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

0x3857d260…b58d

0x065c9d…c394

4 touches
1 conflict

0x123619fc…3488

0x065c9d…c394

3 touches
1 conflict

0x9b668483…b26d

0x065c9d…c394

3 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x9bed6c30…f5ea

0x065c9d…c394

2 touches
0 conflicts

0x9dfac6b4…e4ab

0x065c9d…c394

2 touches
0 conflicts

0xa0754f67…0534

0x065c9d…c394

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 0x3857d26090…d2b58d

← previous block·next block →recent activity