← previous blocknext block →recent activity

Analyzing

Block #70,846,570

13 transactions · 10 stateful · 2026-04-27 10:31:03 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,846,570  ·  13 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

0x18cecf5d…e17e

0x065c9d…c394

4 touches
1 conflict

0x4f85f735…f662

0x065c9d…c394

4 touches
1 conflict

0xd8a0d6bb…b8c9

0x065c9d…c394

4 touches
1 conflict

0xf4ad1291…dec7

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x8956cb26…42fa

0x8c5243…c33e

2 touches
0 conflicts

0x01a89030…f786

0x98dc6e…8633

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: 0x065c9d28…a9c394

1 conflict on slot 0x18cecf5dbd…f0e17e

← previous block·next block →recent activity