Block #70,986,506

← previous blocknext block →recent activity

Analyzing

Block #70,986,506

9 transactions · 8 stateful · 2026-04-28 02:03:02 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,986,506  ·  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

0x661a5fa5…5271

0x065c9d…c394

4 touches
1 conflict

0xcbb00381…b5c5

0x065c9d…c394

4 touches
1 conflict

0xde329166…d6be

0x065c9d…c394

4 touches
1 conflict

0xebc6a5f5…50ac

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

2 touches
0 conflicts

0x452d0f32…76c8

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 0x661a5fa5da…5e5271

← previous block·next block →recent activity