Block #70,381,378

← previous blocknext block →recent activity

Analyzing

Block #70,381,378

16 transactions · 15 stateful · 2026-04-25 06:52:44 UTC

Parallelism

38/100

Blocked

60%

Avg conflicts / tx

2.19

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #70,381,378  ·  16 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

16 touches
28 conflicts

0xf823e97f…2ee6

0x065c9d…c394

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xf823e97f…2ee6

0x131a2e…0da9

6 touches
4 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0x489cb750…7069

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

28 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity