Block #70,986,531

← previous blocknext block →recent activity

Analyzing

Block #70,986,531

11 transactions · 11 stateful · 2026-04-28 02:03:12 UTC

Parallelism

82/100

Blocked

9%

Avg conflicts / tx

0.09

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0x35e90c3c…188d

0x065c9d…c394

4 touches
1 conflict

0x36e9b097…7f39

0x065c9d…c394

4 touches
1 conflict

0x73c15e8f…b6a7

0x065c9d…c394

4 touches
1 conflict

0x7881933e…e75c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x117f4317…f879

0x57ea24…2cec

2 touches
0 conflicts

0x12a42c77…f432

0x57ea24…2cec

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 0x35e90c3c0d…79188d

← previous block·next block →recent activity