Block #70,846,416

← previous blocknext block →recent activity

Analyzing

Block #70,846,416

6 transactions · 6 stateful · 2026-04-27 10:30:02 UTC

Parallelism

50/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,846,416  ·  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

0x16ee19a6…7a81

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x13e81263…6058

0x065c9d…c394

6 touches
3 conflicts

0x57993c58…b448

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0xd0f8a6…badc

6 touches
3 conflicts

0x531131c5…be9f

0x065c9d…c394

6 touches
3 conflicts

0x81128d71…7888

0x065c9d…c394

6 touches
3 conflicts

0x352b1481…53af

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 0x16ee19a6e8…567a81

← previous block·next block →recent activity