Block #70,878,105

← previous blocknext block →recent activity

Analyzing

Block #70,878,105

13 transactions · 11 stateful · 2026-04-27 14:01:09 UTC

Parallelism

62/100

Blocked

64%

Avg conflicts / tx

1.23

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #70,878,105  ·  13 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8e66da19…66b6

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x8e66da19…66b6

0x131a2e…0da9

6 touches
4 conflicts

0x4cb2b152…2e00

0x131a2e…0da9

4 touches
1 conflict

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0x09000000…0001

0x000000…1000

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

10 conflicts on slot 0x8e66da1932…c966b6

← previous block·next block →recent activity