Block #70,986,401

← previous blocknext block →recent activity

Analyzing

Block #70,986,401

6 transactions · 5 stateful · 2026-04-28 02:02:20 UTC

Parallelism

50/100

Blocked

40%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,986,401  ·  6 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x3c5a9674…11e9

0x065c9d…c394

6 touches
3 conflicts

0xff18270a…0ddd

0x065c9d…c394

6 touches
3 conflicts

0xfb8ecb20…7790

0x065c9d…c394

6 touches
3 conflicts

0xec2ca22a…814c

0x065c9d…c394

6 touches
3 conflicts

0x3fbf5124…f0f8

0x065c9d…c394

2 touches
1 conflict

0x3fbf5124…f0f9

0x065c9d…c394

2 touches
1 conflict

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity