Block #70,892,305

← previous blocknext block →recent activity

Analyzing

Block #70,892,305

13 transactions · 11 stateful · 2026-04-27 15:35:39 UTC

Parallelism

85/100

Blocked

18%

Avg conflicts / tx

0.15

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,892,305  ·  13 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

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0x9b7b0c0c…fd5c

0x065c9d…c394

3 touches
1 conflict

0x99f666e3…b2a2

0x3bd359…433a

2 touches
0 conflicts

0x322266fd…529d

0x754704…b603

2 touches
0 conflicts

0x3db9e1f1…cdda

0x754704…b603

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 0xf823e97fa0…262ee6

← previous block·next block →recent activity