← previous blocknext block →recent activity

Analyzing

Block #70,846,462

8 transactions · 7 stateful · 2026-04-27 10:30:20 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,846,462  ·  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

0x268fc30a…6f9c

0x065c9d…c394

4 touches
1 conflict

0x70df7774…a727

0x065c9d…c394

4 touches
1 conflict

0x9fd24ec1…1ffb

0x065c9d…c394

4 touches
1 conflict

0xb52f5a80…5bf2

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x0cfb5d79…7ccb

0x2880ab…7b43

2 touches
0 conflicts

0x0cfb5d79…7ccc

0x2880ab…7b43

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 0x268fc30aba…0c6f9c

← previous block·next block →recent activity