Block #70,922,991

← previous blocknext block →recent activity

Analyzing

Block #70,922,991

14 transactions · 10 stateful · 2026-04-27 19:00:00 UTC

Parallelism

86/100

Blocked

10%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,922,991  ·  14 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

0x5523cac5…3f8f

0x065c9d…c394

4 touches
1 conflict

0x61703ff2…cead

0x065c9d…c394

4 touches
1 conflict

0xc0377b8d…a6bc

0x065c9d…c394

4 touches
1 conflict

0xd8c3f22d…8e47

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xac2a0273…7212

0x34b655…2a6f

2 touches
0 conflicts

0xc3aacf13…6b3d

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 0x5523cac5c3…4f3f8f

← previous block·next block →recent activity