← previous blocknext block →recent activity

Analyzing

Block #70,891,599

14 transactions · 13 stateful · 2026-04-27 15:30:57 UTC

Parallelism

50/100

Blocked

54%

Avg conflicts / tx

1.43

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #70,891,599  ·  14 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5ac9fcfc…f7ff

0x065c9d…c394

4 touches
1 conflict

0xcf3283ba…c9fa

0x065c9d…c394

4 touches
1 conflict

0xf823e97f…2ee6

0x131a2e…0da9

4 touches
1 conflict

0xddcc2574…c522

0x065c9d…c394

3 touches
1 conflict

0xc7081f47…a681

0x065c9d…c394

3 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