← previous blocknext block →recent activity

Analyzing

Block #70,952,046

7 transactions · 6 stateful · 2026-04-27 22:13:25 UTC

Parallelism

71/100

Blocked

17%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,952,046  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5c8c6ab6…dc36

0x131a2e…0da9

4 touches
1 conflict

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x131a2e…0da9

4 touches
1 conflict

0x31b192e7…5700

0x065c9d…c394

2 touches
0 conflicts

0x971c3903…d823

0x065c9d…c394

2 touches
0 conflicts

0x9e972fda…f4a6

0x065c9d…c394

2 touches
0 conflicts

0xb7a3529a…8b39

0x065c9d…c394

2 touches
0 conflicts

0x92d610a6…9a40

0x2a68ba…90c5

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: 0x131a2e70…470da9

1 conflict on slot 0x5c8c6ab6f0…86dc36

← previous block·next block →recent activity