Block #70,995,871

← previous blocknext block →recent activity

Analyzing

Block #70,995,871

10 transactions · 8 stateful · 2026-04-28 03:05:26 UTC

Parallelism

70/100

Blocked

25%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,995,871  ·  10 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…003d

0x065c9d…c394

6 touches
3 conflicts

0xfe352ec6…c6af

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0dfcaece…82e1

0x065c9d…c394

3 touches
1 conflict

0x5d82c9b5…004c

0x3bd359…433a

2 touches
0 conflicts

0x00000000…0004

0x5afd3e…7620

2 touches
0 conflicts

0x0ddc5c66…663e

0x5afd3e…7620

2 touches
0 conflicts

0xc498a3d0…1a04

0x5afd3e…7620

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity