← previous blocknext block →recent activity

Analyzing

Block #70,877,636

9 transactions · 9 stateful · 2026-04-27 13:58:02 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,877,636  ·  9 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

0xa0dbd92f…adbd

0x065c9d…c394

4 touches
1 conflict

0xd0b2a1f8…88ea

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xee025277…c349

0x065c9d…c394

4 touches
1 conflict

0xffd7f22d…fdd9

0x065c9d…c394

3 touches
1 conflict

0xe44a1221…134b

0x065c9d…c394

3 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

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 0xa0dbd92f8d…d1adbd

← previous block·next block →recent activity