← previous blocknext block →recent activity

Analyzing

Block #70,891,622

19 transactions · 17 stateful · 2026-04-27 15:31:06 UTC

Parallelism

79/100

Blocked

29%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #70,891,622  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xcf7e8637…74ea

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x3d57c4df…eba7

0x065c9d…c394

5 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x2f1d9a74…f3fb

0x065c9d…c394

4 touches
1 conflict

0x3b2ea7fc…bc35

0x065c9d…c394

4 touches
1 conflict

0x502a2153…ac58

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

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity