Block #70,986,826

← previous blocknext block →recent activity

Analyzing

Block #70,986,826

9 transactions · 8 stateful · 2026-04-28 02:05:10 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,826  ·  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

0x6e0dc6a1…2922

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0xb1cddb0e…1215

0x065c9d…c394

4 touches
1 conflict

0xaf40174d…0b3b

0x065c9d…c394

3 touches
1 conflict

0x58da399f…575f

0x065c9d…c394

3 touches
1 conflict

0x62a2f515…13a8

0x065c9d…c394

3 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

1 conflict on slot 0x6e0dc6a1eb…bc2922

← previous block·next block →recent activity