Block #70,862,389

← previous blocknext block →recent activity

Analyzing

Block #70,862,389

13 transactions · 13 stateful · 2026-04-27 12:16:28 UTC

Parallelism

54/100

Blocked

46%

Avg conflicts / tx

1.62

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #70,862,389  ·  13 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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x2a354a63…0515

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0x489cb750…7069

0x131a2e…0da9

4 touches
1 conflict

0x2a354a63…0515

0x131a2e…0da9

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x8e66da19…66b6

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity