← previous blocknext block →recent activity

Analyzing

Block #70,845,711

28 transactions · 25 stateful · 2026-04-27 10:25:21 UTC

Parallelism

89/100

Blocked

40%

Avg conflicts / tx

0.46

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,845,711  ·  28 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

0x8e66da19…66b6

0x065c9d…c394

6 touches
3 conflicts

0xd984a5e4…5cfc

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0fff4a9f…b7f6

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x2211a9ff…ccb4

0x34b655…2a6f

4 touches
1 conflict

0x3254d19b…f714

0x34b655…2a6f

4 touches
1 conflict

0x414e9446…4b59

0x34b655…2a6f

4 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 0x8e66da1932…c966b6

← previous block·next block →recent activity