Block #70,878,038

← previous blocknext block →recent activity

Analyzing

Block #70,878,038

23 transactions · 21 stateful · 2026-04-27 14:00:42 UTC

Parallelism

74/100

Blocked

52%

Avg conflicts / tx

1.17

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,878,038  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x4ab14837…e1b2

0x2a68ba…90c5

8 touches
6 conflicts

0x8e66da19…66b6

0x065c9d…c394

6 touches
3 conflicts

0x8e66da19…66b6

0x131a2e…0da9

6 touches
4 conflicts

0x00000000…003d

0x131a2e…0da9

6 touches
3 conflicts

0x89875307…aed2

0x065c9d…c394

4 touches
1 conflict

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity