Block #70,877,908

← previous blocknext block →recent activity

Analyzing

Block #70,877,908

11 transactions · 10 stateful · 2026-04-27 13:59:50 UTC

Parallelism

82/100

Blocked

20%

Avg conflicts / tx

0.27

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,877,908  ·  11 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xc824469a…641c

0x34b655…2a6f

4 touches
1 conflict

0x0f534bde…19c6

0x065c9d…c394

2 touches
0 conflicts

0x3cc0b014…4e47

0x065c9d…c394

2 touches
0 conflicts

0x5c3f2bc9…67d6

0x065c9d…c394

2 touches
0 conflicts

0xb8b2d070…c50f

0x065c9d…c394

2 touches
0 conflicts

0x8e66da19…66b6

0x131a2e…0da9

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 0x0000000000…00003d

← previous block·next block →recent activity