Block #70,922,689

← previous blocknext block →recent activity

Analyzing

Block #70,922,689

6 transactions · 5 stateful · 2026-04-27 18:58:00 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,922,689  ·  6 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

0x61703ff2…cead

0x065c9d…c394

4 touches
1 conflict

0x4fdca318…3adc

0x065c9d…c394

3 touches
1 conflict

0xe81bdf0d…53e7

0x065c9d…c394

3 touches
1 conflict

0x1d003c7b…b055

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x2e11afe0…176b

0x34b655…2a6f

2 touches
0 conflicts

0x3b3a5945…10d0

0x34b655…2a6f

2 touches
0 conflicts

0x4c16b547…71ee

0x34b655…2a6f

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 0x61703ff2d8…96cead

← previous block·next block →recent activity